System and method for intelligent wireless carrier link management system at user equipment devices

ABSTRACT

An information handling system of a management and orchestration module (MANO) may comprise a processor configured to determine user equipment device (UE) connectivity requirements from UE connectivity metrics received from a first UE, for a plurality of UEs managed by the MANO, enterprise profile requirements for the UEs, and detected network conditions of radio access networks (RANs) and cores of an enterprise mobile network. The MANO may also generate an optimal wireless link distribution across the UEs based on the UE connectivity requirements, enterprise profile requirements, and network conditions of the RANs and cores, and determine an antenna configuration adjustment for the first UE, instructing selection of a wireless link via an antenna, selected to meet the UE connectivity requirement relative to wireless links assigned to the other UEs according to the optimal wireless link distribution. A network interface device may transmit the antenna configuration adjustment to the first UE.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to wireless communication foruser equipment devices (UEs) such as mobile computers, embedded systems,vehicles, all-electric and hybrid-electric powered vertical takeoff andlanding (eVTOL), wearables, or smartphones within enterprise mobilenetworks. More particularly, the present disclosure relates tointelligently increasing or decreasing the number and routing ofwireless links established between a UE and an enterprise mobile networkcomprising a plurality of cellular network Radio Access Networks (RANs),non-cellular Access Points (APs) and cores.

BACKGROUND

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to clients is information handling systems. Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes thereby allowing clients to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different clients or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific client or specific use, such as retail,e-commerce, military, disaster management, education, e.g., campusnetworks, financial transaction processing, airline reservations,enterprise data storage, or global communications. In addition,information handling systems may include a variety of hardware andsoftware components that may be configured to process, store, andcommunicate information and may include one or more computer systems,data storage systems, and networking systems remotely available at edgecompute locations or elsewhere in a network to a user equipment (UE)device. The information handling system may include telecommunication,network communication, and video communication capabilities. Variouscomponents of the information handling system may be scaled up or downdynamically by adjusting resources dedicated to operation of suchcomponents over time.

BRIEF DESCRIPTION OF THE DRAWINGS

It will be appreciated that for simplicity and clarity of illustration,elements illustrated in the Figures are not necessarily drawn to scale.For example, the dimensions of some elements may be exaggerated relativeto other elements. Embodiments incorporating teachings of the presentdisclosure are shown and described with respect to the drawings herein,in which:

FIG. 1 is a block diagram illustrating an information handling system ofan enterprise mobile network Management and Orchestration Module (MANO)according to an embodiment of the present disclosure;

FIG. 2 is a block diagram illustrating an enterprise mobile networkcomprising various infrastructure components managed by a MANO accordingto an embodiment of the present disclosure;

FIG. 3 is a block diagram illustrating a 4G Radio Access Network (RAN)and Evolved Packet Core (EPC) according to an embodiment of the presentdisclosure;

FIG. 4 is a block diagram illustrating a 5G RAN according to anembodiment of the present disclosure;

FIG. 5 is a block diagram illustrating 5G network core according to anembodiment of the present disclosure;

FIG. 6 is a block diagram illustrating an information handling system ofa user equipment device (UE) according to an embodiment of the presentdisclosure;

FIG. 7 is a flow diagram illustrating a method of determining a UEantenna configuration adjustment according to an embodiment of thepresent disclosure; and

FIG. 8 is a flow diagram illustrating a method of adjusting wirelesslink antenna configuration at a UE device according to an embodiment ofthe present disclosure.

The use of the same reference symbols in different drawings may indicatesimilar or identical items.

DETAILED DESCRIPTION OF THE DRAWINGS

The following description in combination with the Figures is provided toassist in understanding the teachings disclosed herein. The descriptionis focused on specific implementations and embodiments of the teachings,and is provided to assist in describing the teachings. This focus shouldnot be interpreted as a limitation on the scope or applicability of theteachings.

Information handling systems such as, for example, laptop/notebookcomputing devices, desktop computing devices, tablet computing devices,mobile phones, or other endpoint computing devices known in the art asuser equipment devices (UEs), often utilize wireless networks in orderto exchange data via a plurality of remote cloud networks forming theinternet. Such UEs may communicate via one or more wireless linksestablished between an antenna system of the UE and a cellular basestation (BS) or non-cellular network access point (AP), for example.Large businesses or corporations may establish campuses in whichemployee UEs may establish wireless links to a remote cloud network viaone or more business-operated enterprise mobile networks that includeone or more of enterprise-managed UEs, antenna systems, radio accessnetworks (RANs), and cellular network cores. Such an enterprise mobilenetwork may incorporate infrastructure for establishing wireless linksvia a plurality of wireless communications standards, such as, forexample, 4G cellular, 5G cellular, or non-cellular protocol such asWi-Fi, or Bluetooth®. The mobile network in an embodiment may be managedby a Telco provider, or an enterprise other than a Telco provider.Although the phrase “enterprise mobile network” is used throughout thepresent application, embodiments described herein contemplate any mobilenetwork in which a single entity directs, manages, maintains, orcontrols functionality of a plurality of UEs, one or more RANs, one ormore APs, or one or more network cores.

A single enterprise mobile network may establish wireless links with apool of UEs via one or more of a 4G Radio Access Network (RAN), a 5GRAN, or a non-cellular wireless communication AP. Further,communications received at each of the 4G RAN, 5G RAN, and non-cellularwireless communication AP may be routed to a remote cloud network viaeither a 4G Evolved Packet Core (EPC) or a 5G core. Routing non-cellular(e.g., Wi-Fi) traffic through such a 4G or 5G core may allow UEs thatare not capable of direct communication with the 4G or 5G networks(e.g., not 4G or 5G compatible) to access the higher throughput andlower latency afforded by the 4G or 5G cellular network cores.

Performance of wireless links the UEs maintain within the enterprisemobile network may vary over time, dependent upon several variables. Theaccessibility demands of the UE, such as whether the UE is executingapplications that require higher throughput, lower latency, trafficpattern (burst, linear, asynchronous), level and frequencies of usermobility events, network slice requirements, or heightened securitymeasures may be included within these variables. Also included withinthese variables may be the types of cellular networks (4G or 5G) ornon-cellular networks (e.g., varying Wi-Fi frequency ranges orBluetooth®) supported by the UE. The location of the UE with respect tothe remaining infrastructure of the enterprise mobile network may alsobe a variable, as the distance from the 5G RAN and line-of-sight betweenthe UE and 5G RAN may significantly impact connectivity in the 5G mmWavefrequency band, for example, or coverage maps may vary. Another variablemay be the unique operational capabilities of certain infrastructurecomponents, such as the ability to increase edge computing capacity atthe 4G and 5G cores, and performance of network slicing at the 5G core.Finally, traffic or congestion at any one of the infrastructurecomponents within the 4G RAN, 5G RAN, non-cellular AP, 4G EPC, or 5Gcore may impact throughput or latency of UE communications via theenterprise mobile network. The ways in which each of these variablesimpacts quality of wireless connections with the pool of UEs wirelesslylinked within the enterprise mobile network may vary over time as theapplications executed by these UEs changes, various UEs enter or leavethe pool of linked UEs, the capabilities of the UEs within the poolchanges (e.g., more 4G capable UEs enter and more 5G capable UEs exit),or the locations of various UEs within the pool changes.

The intelligent wireless carrier link management system in embodimentsof the present disclosure addresses these changing conditions across apool of enterprise-managed UEs by determining when each UE within theenterprise-managed pool would benefit from an increase, decrease, orrerouting of wireless links established between that UE and a remotecloud network via an enterprise mobile network. Such determinations maybe made, in various embodiments described herein, as a result of changesin processing capacity at various enterprise mobile networkinfrastructure components, changes in security or power requirements forone or more UEs within the enterprise-managed pool, or on changingconnectivity requirements for one or more UEs within the pool. Forexample, existing systems have addressed the variability of UEconnectivity requirements in the past through a variety of means,including adaptively distributing UE wireless links across availablewireless communications protocols (e.g., handover from cellular toWi-Fi), permanently increasing the number of various types ofinfrastructure components of an enterprise mobile network (e.g., RANcomponents or cellular network core components) in a given area,permanently increasing the number of antennas at such base stations, orupgrading RANs to allow them to establish wireless links in a greaternumber of available bands (e.g., Wi-MAX or 5G mmWave).

The intelligent wireless carrier link management system operating ateach UE within the enterprise mobile network in an embodiment mayaddress these changing connectivity requirements by adaptively adjustingthe wireless link antenna configuration at each UE to ensure theconnectivity afforded by those wireless links meets the changingconnectivity requirements of the UE over time. The intelligent wirelesscarrier link management system at individual UEs in embodiment describedherein may routinely gather connectivity metrics and requirementsdescribing currently executing software applications, securityrequirements, or power metrics for that UE. Connectivity metricsdescribing Quality of Service (QoS) measurements for available wirelesslinks and connectivity requirements (e.g., throughput, latency, droppedpackets, etc.) for performance of currently executing softwareapplications may also be routinely monitored or gathered by theintelligent wireless carrier link management system in embodimentsdescribed herein. Location position, trajectory and speed may bemonitored and gathered, too. The intelligent wireless carrier linkmanagement system may determine adjustments to wireless link antennaconfigurations may be necessary in order to ensure the connectivityrequirements at the UE continue to be met, based upon changes to theconnectivity metrics routinely gathered in such a way. Such wirelesslink antenna configuration adjustments in embodiments described hereinmay include activation or deactivation of antennas at the UE, routing orrerouting of wireless links from the UE to various RANs or non-cellularAPs within the enterprise mobile network, or network slicing to routedata transceived pursuant to execution of specific software applicationsat the UE through a specifically identified antenna at the UE, forexample.

Wireless link antenna configuration adjustments in embodiments describedherein may also be determined by a Management and Orchestration Module(MANO) operating remotely from each of the UEs within the enterprisemobile network. Such determinations may be made, in various embodimentsdescribed herein, in order to leverage changes in capacity at variousinfrastructure components of the RANs, non-cellular APs, and corescomprising the enterprise mobile network. The MANO may make suchdeterminations and instruct adjustments at individual UEs to optimizeperformance across each of these infrastructure components and the poolof UEs communicating within the network. For example, the MANO mayorchestrate functionality of the plurality of RANs and cellular networkcores within an enterprise mobile network and assess the communicationneeds for a pool of enterprise-managed UEs wirelessly linked within suchan enterprise mobile network. The MANO may then scale up or increaseantenna systems or computing resources of various RANs or APs whilescaling down or decreasing antenna systems or computing resources atother RANs or APs to increase the ability of the enterprise mobilenetwork infrastructure to establish wireless links capable of satisfyingconnectivity requirements. Such scaling of the enterprise mobile networkinfrastructure components may prompt the MANO in embodiments of thepresent disclosure to increase, decrease, or reroute wireless links atone or more UEs communicating via the enterprise mobile network in orderto take advantage of the optimized scaling of various enterprise mobilenetwork infrastructure components.

The determination that a UE communicating within the enterprise mobilenetwork requires fewer or greater wireless links, or rerouting of suchlinks (e.g., as described directly above) may be made in variousembodiments described herein at a computing node co-located with theMANO, or by the intelligent wireless carrier link management systemoperating at one of the UEs. Upon determination by the intelligentwireless carrier link management system or MANO in embodiments describedherein that a UE communicating within the enterprise mobile networkrequires fewer or greater wireless links, or rerouting of such links,the intelligent wireless carrier link management system may operate,either alone or in tandem with the MANO, to accordingly adjust wirelesslinks at one or more UEs. For example, the MANO in embodiments whereinadditional wireless links are deemed necessary at an individual UE mayactivate an additional antenna at the individual enterprise-managed UE,and establish an additional wireless link via this additional antenna.The enterprise-managed UE in some embodiments described herein may beinstructed by the MANO to establish such an additional wireless linkwith a specifically identified RAN, non-cellular AP, or cellular networkcore identified by the MANO as most likely to optimize distribution ofprocessing resources and connectivity performance across a plurality ofwireless links established within the enterprise mobile network by aplurality of enterprise-managed UEs.

The intelligent wireless carrier link management system in embodimentsmay also work alone or in tandem with the MANO to terminate wirelesslinks at one or more UEs and deactivate antennas through which thosewireless links are currently transceiving in various conditions. Forexample, wireless links established specifically for the purposes ofsecure data transmission may cease to be necessary when suchtransmission ends. As another example, wireless links established inorder to optimize throughput or latency of communication for a given UEmay be terminated when software applications requiring such throughputor latency metrics cease to execute at the UE. In such a way, and invarious other embodiments described herein, the intelligent wirelesscarrier link management system may operate in tandem with a MANO of anenterprise mobile network to establish fewer or greater wireless links,or rerouting of such links by any one of a plurality ofenterprise-managed UEs communicating via the enterprise mobile networkin response to changing capabilities and demands of various UEs andinfrastructure components across the enterprise mobile network.

FIG. 1 illustrates an information handling system 100 of a Managementand Orchestration Module (MANO) 130 operating within an enterprisemobile network, or at edge computing for local management andorchestration or at a remote server for global management orchestrationand testing according to embodiments described herein. As describedherein, the enterprise mobile network may wireless couple to a pool 117of enterprise-managed UEs in various embodiments described herein. Theenterprise mobile network and multi-access edge computing (MEC)resources may be managed by enterprise IT professionals via the MANO130. The MANO 130 in an embodiment may establish fewer or greaterwireless links, or rerouting of such links by any one of a plurality ofenterprise-managed UEs within pool 117 communicating via the enterprisemobile network. Such adjustments may be instructed at the UEs by theMANO in response to changing capabilities and demands of various UEs andinfrastructure components across the enterprise mobile network.

The pool of UEs 117 may communicate via one or more wireless linksestablished by an antenna system of one of the pool of UEs 117 forcommunication within the enterprise mobile network for example. Largebusinesses or corporations may establish campuses in which employee UEs(e.g., within the pool 117) may establish wireless links to the remotecloud network 150, or MEC resources via one or more business-operatedenterprise wireless communication interface devices (e.g., 140). Asdescribed in greater detail with respect to FIG. 2 , below, suchenterprise mobile networks may incorporate infrastructure forestablishing wireless links via a plurality of wireless communicationsstandards, such as, for example, 4G cellular, 5G cellular, ornon-cellular protocols such as Wi-Fi, or Bluetooth®. In such cases, asingle enterprise mobile network executing a MANO 130 may establishwireless links with the pool of UEs 117 via one or more of the 4G RadioAccess Network (RAN), the 5G RAN, a non-cellular wireless communicationAP, or future wireless protocol RANs. Further, communications receivedat each of the 4G RAN, 5G RAN, and non-cellular wireless communicationAP may be routed to a remote cloud network 150 via either a 4G EvolvedPacket Core (EPC) or a 5G core. The MANO 130 in an embodiment mayorchestrate performance at and between each of these non-cellular APs,RANs, and cores.

In the embodiments described herein, an information handling systemincludes any instrumentality or aggregate of instrumentalities operableto compute, classify, process, transmit, receive, retrieve, originate,switch, store, display, manifest, detect, record, reproduce, handle, oruse any form of information, intelligence, or data for business,scientific, control, entertainment, or other purposes. For example, aninformation handling system can be a personal computer, mobile device(e.g., smart phone, connected/autonomous vehicle, smart watches,wireless surveillance systems, wireless point of sale devices, drones),server (e.g., blade server or rack server), a consumer electronicinformation handling system, a network server or storage device, anetwork router, switch, or bridge, wireless router, or other networkcommunication information handling system, a network connected device(cellular telephone, tablet information handling system, etc.), IoTcomputing device, wearable computing device, a set-top box (STB), amobile device, a palmtop computer, a laptop computer, a desktopcomputer, a communications device, an access point (AP), a base stationtransceiver, a wireless telephone, a land-line telephone, a controlsystem, a camera, a scanner, a facsimile machine, a printer, a pager, apersonal device, a web appliance, or any other suitable machine capableof executing a set of instructions (sequential or otherwise) thatspecify actions to be taken by that machine, and can vary in size,shape, performance, price, and functionality.

In a networked deployment, the information handling system 100 mayoperate in the capacity of a server or as a client computer in aserver-client network environment, or as a peer computer system in apeer-to-peer (or distributed) network environment. In a particularembodiment, the computer system 100 can be implemented using electronicinformation handling systems that provide voice, video or datacommunication. For example, an information handling system 100 may beany mobile or other computing device capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that machine. Further, while a single information handling system 100is illustrated, the term “system” shall also be taken to include anycollection of systems or sub-systems that individually or jointlyexecute a set, or multiple sets, of instructions to perform one or morecomputer functions.

The information handling system can include memory (volatile (e.g.,random-access memory, etc.), nonvolatile (read-only memory, flash memoryetc.) or any combination thereof), one or more processing resources,such as a central processing unit (CPU), a graphics processing unit(GPU), hardware or software control logic, or any combination thereof.Additional components of the information handling system can include oneor more storage devices, one or more communications ports forcommunicating with external devices, as well as various input and output(I/O) devices, such as a keyboard, a mouse, a video/graphic display, orany combination thereof. The information handling system can alsoinclude one or more buses operable to transmit communications betweenthe various hardware components. Portions of an information handlingsystem may themselves be considered information handling systems.

More specifically, the information handling system 100 may orchestrateexecution of a single node as well as a plurality of computing nodes,pods, clusters, or containers capable of performing computing tasksindividually, or in combination with one another. In particular, severalaspects of the 4G Radio Access Network (RAN), the 4G EPC, the 5G core,and the 5G RAN may function as containerized software applicationsexecuted by one or more runtime engines and orchestrated by the MANO130. These runtime engines may be executed by one or more processors ofa multi-access edge computing platform (MEC) described in greater detailwith respect to FIG. 2 below. MEC system resources may be represented bythe information handling system 100 of FIG. 1 . MEC system resources mayinclude the processor 102, which functions in an embodiment to executecode instructions of the MANO 130 or other applications requiringlow-latency for one or more of the pool of UEs 112. The MEC processorsmay also operate to execute code instructions of various components ofthe 4G RAN, 5G RAN, 4G EPC, and 5G core for switching, network routeselection, authentication, and other functions.

The 5G core, for example, processes data packets received from or enroute to a UE (e.g., within pool 117) by executing containerized codeinstructions of an access and mobility management function (AMF), usingMEC processor resources, to make application programming interface (API)calls to other 5G core network functions that each perform one or moredata packet preparation steps. Thus, as described in greater detail withrespect to FIG. 5 below, the AMF orchestrates execution of a pluralityof other containerized 5G core network functions on each data packetreceived. The MANO 130 in an embodiment may assign specific processorsof the MEC system represented by information handling system 100 to theexecution of specifically identified 5G core network functions, or toother processing functions of the 4G RAN, 5G RAN, or 4G EPC, forexample. The processor 102 in some embodiments may be a server systemeither in a remote cloud or locally at a MEC information handling systemthat execute code instructions of the MANO 130 to perform such anassignment. The MANO 130 may also limit the number of calls that each ofthese RANs or core functions may make to each of those assignedprocessors, or limit the number of nodes or pods hosting such functions.

The use of containerized software applications facilitates anabstraction or separation between the user of a software application(e.g., the AMF making API calls to the other 5G core network functions),the software application itself (the containerized 5G core networkfunctions), and the computing environment (e.g., computing cluster) inwhich the software application is executing. As described in greaterdetail herein with respect to FIGS. 3 and 4 , the serving gateway (S-GW)and packet data network gateway (P-GW) of the 4G EPC, the evolved Node B(eNodeB) of the 4G RAN, and the logical 5G radio node (gNodeB) of the 5GRAN may similarly operate through execution of containerized softwareapplications. Thus, portions of the 4G RAN, the 5G RAN, 4G EPC, and the5G network core in various embodiments described herein may each operateone or more computing nodes, pods, or clusters of computing resourcesfor processing data packets via execution of containerized softwareapplications using MEC memory and processing resources.

These computing nodes, pods, clusters, or containers in an embodimentmay store an “image,” or compiled, executable set of code instructionsfor the containerized software application. A run-time engine may accessand execute these compiled, executable sets of code instructionsaccording to calls made by a base band unit in the case of 4G RAN (asdescribed in greater detail with respect to FIG. 3 ), an S-GW or P-GW ofthe 4G EPC (as described in greater detail with respect to FIG. 3 ), aRAN intelligent controller node in the case of 5G RAN (as described ingreater detail with respect to FIG. 4 ), or the AMF at the 5G core(e.g., as described in greater detail with respect to FIG. 5 ). Each ofthese components capable of executing such run-time engines may furtherreceive control instructions from the MANO 130 to increase or decreasethe computing resources (e.g., MEC processor or memory availability,number of pods, number of clusters, number of nodes, number ofcontainerized software application image replicas) dedicated to theprocessing of data packets according to each of the supported wirelesscommunication standards or protocols (as described in greater detailwith respect to FIG. 2 below). In other words, the MANO 130 may operateto increase or decrease the MEC computing resources made available foruse by the 4G RAN, the 4G EPC, the 5G RAN, or the 5G core.

Software application containerization separates node configurationinstructions from the code instructions for executing the underlyingcontainerized software application (e.g., 4G EPC S-GW, MME and HSS, orP-GW, 5G core network functions, eNodeB functions, or gNodeB functions),allowing users to deploy the underlying containerized softwareapplication to any number of computing clusters or nodes. As softwarecontainerization has gained popularity, containerized applicationdeployment tools, such as container-orchestration systems for automatingcomputing application deployment, scaling, and management across severalnodes or several clusters have emerged. The MANO 130 in an embodimentmay incorporate such container-orchestration system functionality. Forexample, the MANO 130 in an embodiment may facilitate and managedelivery to a deployment cluster for the 5G network core of clusterconfiguration files to execute a containerized software application(e.g., 5G core network function), and immutable images of the underlyingsoftware application container (e.g., 5G core network function).

Each information handling system 100 may also represent a node that maycomprise a separate MEC computing machine, and may contain one or morecomputing pods, each comprising at least a MEC processor 102 and MECmemory 103. Each pod may execute at least one containerized softwareapplication (e.g., a 5G core network function or other enterprise lowlatency software applications for UEs in pool 117). A single minion nodemay execute multiple pods, with each pod executing a different instanceof the same containerized software application (e.g., a first instanceof a 5G core network function, and a replica of the same 5G core networkfunction). This may allow the minion node to quickly scale and balancethe load of calls to the containerized software application across aplurality of pods, as well as decrease any downtime associated with bugsor errors occurring at a single pod. In other words, by scaling thenumber of nodes, pods, clusters, or containers executing any given 5Gcore network function (or any eNodeB or gNodeB functions), the MANO 130may scale up or scale down the computing resources dedicated toprocessing data packets according to a specific UE-requested protocol(e.g., 4G, 5G, or non-cellular).

Information handling system 100 can include devices or modules thatembody one or more of the devices or execute instructions for the one ormore systems and modules described above, and operates to perform one ormore of the methods described above. The information handling system 100may execute code instructions 132 that may operate on local or remoteservers or systems, remote cloud networks, or on-box in individualclient information handling systems according to various embodimentsherein. In some embodiments, it is understood any or all portions ofcode instructions 132 may operate on a plurality of information handlingsystems 100.

The information handling system 100 may include a processor 102 such asa central processing unit (CPU), control logic or some combination ofthe same. Any of the processing resources may operate to execute codethat is either firmware or software code. Moreover, the informationhandling system 100 can include memory such as main memory 104, staticmemory 106, computer readable medium 131 storing instructions 132 of theMANO 130, and drive unit 116 (volatile (e.g., random-access memory,etc.), nonvolatile (read-only memory, flash memory etc.) or anycombination thereof). The information handling system 100 can alsoinclude one or more buses 108 operable to transmit communicationsbetween the various hardware components such as any combination ofvarious input and output (I/O) devices.

As shown, the information handling system 100 may further include avideo display device 110. The video display device 110 in an embodimentmay function as a liquid crystal display (LCD), an organic lightemitting diode (OLED), a flat panel display, or a solid-state display.Additionally, the information handling system 100 may include an alphanumeric input device 112, such as a keyboard, and/or a cursor controldevice, such as a mouse, touchpad, or gesture or touch screen inputdevice. The information handling system 100 can also include a diskdrive unit 116.

The network interface device 130 may provide connectivity of theinformation handling system 100 to one or more UEs (e.g., within pool117) via one or more LAN or WAN communication links in the case of anenterprise local or remote server as information handling system 100 inan embodiment. As described in greater detail herein, each UE in thepool 117 may communicate with the MANO 130 (e.g., either through wiredconnection, wireless connection with the 4G RAN, 5G RAN, or AP, orout-of-band (00B) communications) to share gathered connectivity metricsfor wireless links established by that UE, connectivity metricsdescribing currently executing software applications at the UE, securityrequirements for UE wireless communication, power consumption metrics atthe UE, connectivity metrics, or UE location data for determining UEconnectivity requirements.

The network interface device 130 may provide connectivity to a Wide AreaNetwork (WAN), a Wireless Wide Area Network (WWAN) communicationnetwork, a private LTE communication network, a 4G LTE publiccommunication network, or a 5G millimeter-wave (mm-wave) communicationnetwork, or other cellular communication networks in the case of aninformation handling system 100 operating as an AP or cellular RAN insome embodiments. Connectivity of the information handling system 100 tothe pool 117 of UE devices or to any of a plurality of remote cloudnetworks 150 in an embodiment may be via wired or wireless connection.In some aspects of the present disclosure, the network interface device130 may operate two or more wireless links. In other aspects of thepresent disclosure, the information handling system 100 may include aplurality of network interface devices 130, each operating separateradio subsystems 141.

The network interface device 130 may operate in accordance with anycellular wireless data communication standards. Network interface device130, in an embodiment, may connect to any combination of macro-cellularwireless connections including 2G, 2.5G, 3G, 4G, 5G or the like from oneor more service providers, including an enterprise managed RAN.Utilization of radiofrequency communication bands according to severalexample embodiments of the present disclosure may include bands usedwith the WWAN standards, which may operate in both licensed andunlicensed spectrums. More specifically, the network interface device130 in an embodiment may transceive within radio frequencies associatedwith the 5G New Radio (NR) Frequency Range 1 (FR1) or Frequency Range 2(FR2). NRFR1 may include radio frequencies below 6 GHz, associated with4G LTE and other standards predating the 5G communications standards nowemerging. NRFR2 may include radio frequencies above 6 GHz, madeavailable within the now emerging 5G communications standard.Communications within NRFR1 may be enabled through the use of either anevolved Node B (eNodeB) of a 4G RAN (as described in greater detail withrespect to FIG. 3 ) in combination with the 4G EPC, or the 5G networkcore (as described in greater detail with respect to FIG. 5 ), or alogical 5G radio node (gNodeB) of the 5G RAN (as described in greaterdetail with respect to FIG. 4 ), in combination with the 5G networkcore.

Frequencies related to the 5G networks may include low-frequency (e.g.,below 1 GHz), mid-frequency (e.g., between 1 GHz and 6 GHz) andhigh-frequency (HF) (e.g., above 6 GHz) bands. Citizen's BroadbandSpectrum (CBRS) operating within the mid-frequency band (e.g., 3.5 Ghz)may be included as well. WWAN may use the Unlicensed NationalInformation Infrastructure (U-NII) band which typically operates in the˜5 GHz frequency band such as 802.11 a/h/j/n/ac/ax (e.g., centerfrequencies between 5.170-5.785 GHz). It is understood that any numberof available channels may be available under the 5 GHz sharedcommunication frequency band. WWAN may operate in a number of bands,some of which are proprietary but may include a wireless communicationfrequency band at approximately 2.5 GHz band for example. In additionalexamples, WWAN carrier bands may operate at frequency bands ofapproximately 700 MHz, 800 MHz, 1900 MHz, or 1700/2100 MHz for exampleas well.

In an embodiment, the network interface device 130 may becommunicatively coupled to an array of antenna systems 143. The antennacontroller 142 may monitor wireless link state information, wirelesslink configuration data, network slice data, or other input data togenerate channel estimation and determine antenna radiation patterns.The network interface device 130 in an embodiment may further include aradio subsystem 141 which may operate to modulate and demodulate signalstransceived within a WWAN or WLAN format, set signal transmission powerlevels or sensitivity to signal reception, select channels or frequencybands, and conduct other functions in support of a wireless transmissionfrom the pool of UEs 117 to 4G EPC 150 or the 5G network core 170.

The network interface device 130 in an embodiment may also provideconnectivity to a WLAN network that may be a wired local area network(LAN), a wireless personal area network (WPAN), a public WiFicommunication network, a private WiFi communication network, a publicWiMAX communication network, a Bluetooth® communication network, or anyother non-cellular (non-3GPP) communication networks. To communicatewith a wireless local area network, standards including IEEE 802.11 WLANstandards, IEEE 802.15 WPAN standards, WiMAX, Bluetooth®, or similarwireless standards may be used. Utilization of radiofrequencycommunication bands according to several example embodiments of thepresent disclosure may include bands used with the WLAN standards whichmay operate in both licensed and unlicensed spectrums. For example, WLANmay use the Unlicensed National Information Infrastructure (U-NII) bandwhich typically operates in the ˜5 MHz frequency band such as 802.11a/h/j/n/ac (e.g., center frequencies between 5.170-5.785 GHz). It isunderstood that any number of available channels may be available underthe 5 GHz shared communication frequency band. WLAN, for example, mayalso operate at a 2.4 GHz band, or a 60 GHz band.

The information handling system 100 may further include a powermanagement unit (PMU) 114 (a.k.a. a power supply unit (PSU)). The PMU114 may manage the power provided to the components of the informationhandling system 100 such as the processor 102 such as a CPU or embeddedcontroller, a cooling system, one or more drive units 116, a graphicalprocessing unit (GPU), a video/graphic display device or otherinput/output devices 112, and other components that may require powerwhen a power button has been actuated by a user. In an embodiment, thePMU 114 may monitor power levels and be electrically coupled to theinformation handling system 100 to provide this power and coupled to bus108 to provide or receive data or instructions.

Information handling system 100 includes one or more of an operatingsystem (OS), and basic input/output system (BIOS) firmware/software orapplication programs that may be executable instructions 132 executed atany processor 102 and stored at one or more memory devices 104, 106, or116. BIOS firmware/software functions to initialize information handlingsystem 100 on power up, to launch an OS, and to manage input and outputinteractions between the OS and the other elements of informationhandling system 100. In a particular embodiment, BIOS firmware/softwareresides in memory 104, and include machine-executable code that isexecuted by processor 102 to perform various functions of informationhandling system 100 as described herein. In another embodiment (notillustrated), application programs and BIOS firmware/software reside inanother storage medium of information handling system 100. For example,application programs and BIOS firmware/software can reside in drive 116,in a ROM (not illustrated) associated with information handling system100, in an option-ROM (not illustrated) associated with various devicesof information handling system 100, in a storage system (notillustrated) associated with network channel of the network interfacedevice 130, in another storage medium of information handling system100, or a combination thereof. Executable code instructions 132 forapplication programs and BIOS firmware/software can each be implementedas single programs, or as separate programs carrying out the variousfeatures as described herein.

In some embodiments, software, firmware, dedicated hardwareimplementations such as application specific integrated circuits,programmable logic arrays and other hardware information handlingsystems can be constructed to implement one or more of the methodsdescribed herein. Applications that may include the apparatus andsystems of various embodiments can broadly include a variety ofelectronic and computer systems. One or more embodiments describedherein may implement functions using two or more specific interconnectedhardware modules or information handling systems with related controland data signals that can be communicated between and through themodules, or as portions of an application-specific integrated circuit.Accordingly, the present system encompasses software, firmware, andhardware implementations.

In accordance with various embodiments of the present disclosure, themethods described herein may be implemented by firmware or softwareprograms executable by a controller or a processor system. Further, inan exemplary, non-limited embodiment, implementations can includedistributed processing, component/object distributed processing, andparallel processing. Alternatively, virtual computer system processingcan be constructed to implement one or more of the methods orfunctionality as described herein.

The present disclosure contemplates a computer-readable medium thatincludes instructions, parameters, and profiles 132 or receives andexecutes instructions, parameters, and profiles 132 responsive to apropagated signal. The information handling system 100 can include a setof instructions 132 that can be executed to cause the computer system toperform any one or more of the methods or computer-based functionsdisclosed herein. For example, instructions 132 may execute a MANO 130in an embodiment to establish fewer or greater wireless links, orrerouting of such links by any one of a plurality of enterprise-managedUEs in pool 117 communicating via the enterprise mobile network inresponse to changing capabilities and demands of various UEs in pool 117and infrastructure components across the enterprise mobile network.Various software modules comprising application instructions 132 may becoordinated by an operating system (OS), and/or via one or moreapplication programming interfaces (APIs). An example operating systemmay include Windows®, Android®, and other OS types known in the art.Example APIs may include Win 32, Core Java API, or Android APIs.

The disk drive unit 116 and may include a computer-readable medium 131in which one or more sets of instructions 132 such as software can beembedded to be executed by the processor 102 and antenna controller 142to perform the processes described herein. Similarly, main memory 104and static memory 106 may also contain a computer-readable medium forstorage of one or more sets of instructions, parameters, or profiles132. The disk drive unit 116 or static memory 106 also contain space fordata storage. Further, the instructions 132 may embody one or more ofthe methods or logic as described herein. In a particular embodiment,the instructions, parameters, and profiles 132 may reside completely, orat least partially, within the main memory 104, the static memory 106,and/or within the disk drive 116 during execution by the processor 102or an antenna controller (e.g., 142) of information handling system 100.The main memory 104 and the processor 102 also may includecomputer-readable media.

Main memory 104 or other memory of the embodiments described herein maycontain computer-readable medium (not shown), such as RAM in an exampleembodiment. An example of main memory 104 includes random access memory(RAM) such as static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM(NV-RAM), or the like, read only memory (ROM), another type of memory,or a combination thereof. Static memory 106 may containcomputer-readable medium (not shown), such as NOR or NAND flash memoryin some example embodiments. The drive unit 116 may include access to acomputer-readable medium 131 such as a magnetic disk or flash memory inan example embodiment. While the computer-readable medium is shown to bea single medium, the term “computer-readable medium” includes a singlemedium or multiple media, such as a centralized or distributed database,and/or associated caches and servers that store one or more sets ofinstructions. The term “computer-readable medium” shall also include anymedium that is capable of storing, encoding, or carrying a set ofinstructions for execution by a processor or that cause a computersystem to perform any one or more of the methods or operations disclosedherein.

In a particular non-limiting, exemplary embodiment, thecomputer-readable medium can include a solid-state memory such as amemory card or other package that houses one or more non-volatileread-only memories. Further, the computer-readable medium can be arandom-access memory or other volatile re-writable memory. Additionally,the computer-readable medium can include a magneto-optical or opticalmedium, such as a disk or tapes or other storage device to storeinformation received via carrier wave signals such as a signalcommunicated over a transmission medium. Furthermore, a computerreadable medium can store information received from distributed networkresources such as from a cloud-based environment. A digital fileattachment to an e-mail or other self-contained information archive orset of archives may be considered a distribution medium that isequivalent to a tangible storage medium. Accordingly, the disclosure isconsidered to include any one or more of a computer-readable medium or adistribution medium and other equivalents and successor media, in whichdata or instructions may be stored.

In other embodiments, dedicated hardware implementations such asapplication specific integrated circuits, programmable logic arrays andother hardware devices can be constructed to implement one or more ofthe methods described herein. Applications that may include theapparatus and systems of various embodiments can broadly include avariety of electronic and computer systems. One or more embodimentsdescribed herein may implement functions using two or more specificinterconnected hardware modules or devices with related control and datasignals that can be communicated between and through the modules, or asportions of an application-specific integrated circuit. Accordingly, thepresent system encompasses software, firmware, and hardwareimplementations.

When referred to as a “system”, a “device,” a “module,” a “controller,”or the like, the embodiments described herein can be configured ashardware. For example, a portion of an information handling systemdevice may be hardware such as, for example, an integrated circuit (suchas an Application Specific Integrated Circuit (ASIC), a FieldProgrammable Gate Array (FPGA), a structured ASIC, or a device embeddedon a larger chip), a card (such as a Peripheral Component Interface(PCI) card, a PCI-express card, a Personal Computer Memory CardInternational Association (PCMCIA) card, or other such expansion card),or a system (such as a motherboard, a system-on-a-chip (SoC), or astand-alone device). The system, device, controller, or module caninclude software, including firmware embedded at a device, such as anIntel® Core class processor, ARM® brand processors, Qualcomm® Snapdragonprocessors, or other processors and chipsets, or other such devices, orsoftware capable of operating a relevant environment of the informationhandling system. The system, device, controller, or module can alsoinclude a combination of the foregoing examples of hardware or software.Note that an information handling system can include an integratedcircuit or a board-level product having portions thereof that can alsobe any combination of hardware and software. Devices, modules,resources, controllers, or programs that are in communication with oneanother need not be in continuous communication with each other, unlessexpressly specified otherwise. In addition, devices, modules, resources,controllers, or programs that are in communication with one another cancommunicate directly or indirectly through one or more intermediaries.

FIG. 2 is a block diagram illustrating connectivity of a pool of userequipment devices (UEs) to a remote cloud network, via an enterprisemobile network comprising various and plural managed RAN, cellularnetwork core, and MEC infrastructure components managed by a managementand orchestration module (MANO) according to an embodiment of thepresent disclosure. As described herein, information handling systems,or user equipment devices (UEs) (e.g., within a pool 210) often utilizewireless networks in order to exchange data via a plurality of remotecloud networks (e.g., 250) forming at least a portion of the internet.Such UEs may communicate via one or more wireless links (e.g., 220)established between the UE and one or more business-operated enterpriseRAN and core infrastructure modules (e.g., 230). For example, enterpriseRAN and core infrastructure module 230 may incorporate infrastructurefor establishing wireless links via a plurality of wirelesscommunications standards, such as, for example, 4G cellular, 5Gcellular, or non-cellular protocol such as Wi-Fi, or Bluetooth®. In suchcases, a single enterprise RAN and core infrastructure module 230 mayestablish wireless links with a pool 210 of UEs via one or more of a 4GRadio Access Network (RAN) 231, a 5G RAN 232, or a non-cellular wirelesscommunication AP 233. Further, communications received at each of the 4GRAN 231, 5G RAN 232, and non-cellular wireless communication AP 233 maybe routed to a remote cloud network 250 via either a 4G Evolved PacketCore (EPC) 234 or a 5G core 235 and a wired backhaul connection 240(e.g., SG1-U interface or N6 interface defined by the technicalspecifications 3GPP TS 23.88 and 3GPP TS 23.501, respectively).

Each of these enterprise mobile network infrastructure components (e.g.,231, 232, 233, 234, or 235) may utilize processors and memory of aMulti-Access Edge Computing Platform (MEC) 238, or other processingresources co-located at the enterprise RAN and core infrastructure 230in order to execute their required processing of data frames or packets.In other words, ability of each of the enterprise mobile networkinfrastructure components (e.g., 231, 232, 233, 234, or 235) to performmay hinge upon the volume and quality of MEC 238 resources madeavailable to it. Thus, the overall quality (e.g., as measured by QoSmetrics such as latency, throughput, or dropped packets) of connectivitybetween the UE pool 210 and services 251 or software applications 252 atthe remote cloud network 250 or edge services 242 or edge softwareapplications 243 in an embodiment may be impacted by configuration andexecution of the 4G RAN 231, 5G RAN 232, Wi-Fi AP 233, 4G EPC 234, 5Gcore 235, and MEC 238, and by routing of communications between andamong each of these enterprise mobile network infrastructure components(e.g., 231, 232, 233, 234, or 235). The Management and OrchestrationModule 236 and the intelligent wireless carrier link management system237 in an embodiment may operate to adaptively optimize suchinfrastructure configurations and traffic routing to provide the bestoverall connectivity between the UE pool 210 and the remote cloudnetwork 250 or local MEC resources 258 as the demands of those UEs inpool 210 change over time.

The UE pool 210 may include several different types of mobile devices,each with different networking capabilities. For example, the pool 210may include 4G UEs 211 that are capable of communication via the 4Gcellular communications standard, 5G UEs 212 that are capable ofcommunication via the 5G cellular communications standard, or Wi-Fi UEs213 that are capable of communication via non-cellular (e.g., non-3GPP)communications standards such as Wi-Fi, Bluetooth®, and Near FieldCommunication (NFC). Some UEs within pool 210 may comprise 4G UEs 211and 5G UEs 212, if such UEs are capable of communication according toboth of these standards. As another example, some UEs within pool 210may be capable of communication according to both the 4G communicationsstandard and the non-cellular (e.g., Wi-Fi) standard, such that thoseUEs comprise both 4G UEs 211 and Wi-Fi UEs 213. In yet another example,some UEs within pool 210 may be capable of communication according toboth the 5G communications standard and the non-cellular (e.g., Wi-Fi)standard, such that those UEs comprise both 5G UEs 212 and Wi-Fi UEs213. In still another example, some UEs within pool 210 may be capableof communication according to the 4G communications standard, the 5Gcommunications standard, and the non-cellular (e.g., Wi-Fi) standard,such that those UEs comprise both 4G UEs 211, 5G UEs 212, and Wi-Fi UEs213. It is contemplated that various UEs in pool 210 may have anycombination of wireless capabilities in some embodiments.

Each of the UEs in pool 210 may execute an intelligent wireless carrierlink management system 214 of the MANO 236. These intelligent wirelesscarrier link management systems 214 in an embodiment may communicatewith the MANO 236 located at the enterprise RAN and core infrastructuremodule 230 and managed by the enterprise to gather connectivity metricsand connectivity requirements for each of the UEs within pool 210. Suchcommunication may occur via wireless links 220 established between thepool of UEs 210 and one or more of the 4G RAN231, 5G RAN 232 or Wi-Fi AP233, or via wired or wireless out-of-band (00B) communications 221directly between the MANO 236 and the intelligent wireless carrier linkmanagement system 214 in an embodiment. This data, along with datagathered at the various infrastructure components (e.g., 231, 232, 233,234, or 235) of the enterprise RAN and core infrastructure module 230may be used to determine current and desired connectivity between the UEpool 210 and the remote cloud network 250.

Connectivity metrics of the UEs in pool 210 in an embodiment maydescribe currently executing software applications at each of the UEs,battery power remaining at each of the UEs, or security requirements foreach of the UEs, for example. Connectivity metrics in an embodiment foreach UE may include measurements of various quality of service (QoS)variables for established wireless links (e.g., 220), including, forexample, latency, throughput, dropped packets, security levels (e.g.,Virtualized Private Network (VPN) tunnels), or network slicedesignations. Connectivity requirements for each UE in pool 210 maydescribe available types of wireless radios of the UEs. Connectivityrequirements for each UE in pool 210 in an embodiment may furtherdescribe QoS requirements for each UE, as defined by policies associatedwith each UE, or as determined by the MANO 236 or the intelligentwireless carrier link management system 214 based on currently executingsoftware applications at each of the UEs in pool 210.

Each of these variables may impact overall quality of communicationsbetween the pool of UEs 210 and the remote cloud network 250 in anembodiment. For example, accessibility demands of the UEs in pool 210,such as whether the UE is executing applications that require higherthroughput, lower latency, or heightened security measures may beincluded within these variables. Also included within these variablesmay be the types of cellular networks (4G or 5G) or non-cellularnetworks (e.g., varying Wi-Fi frequency ranges or Bluetooth®) supportedby the UE. The location of the UE with respect to the enterprise RAN andcore infrastructure module 230 may also be a variable, as the distancefrom the 5G RAN 232 and line-of-sight between the UE and 5G RAN 232 maysignificantly impact connectivity in the 5G mmWave frequency band, forexample, or coverage maps may vary for other RANs 231 or 235. Anothervariable may be the unique operational capabilities of certaininfrastructure components, such as the ability to increase edgecomputing (e.g., MEC 238) capacity at the 4G EPC 234 and 5G core 235,and performance of network slicing at the 5G core 235. Finally, trafficor congestion at any one of the infrastructure components within the 4GRAN 231, 5G RAN 232, non-cellular AP 233, 4G EPC 234, or 5G core 235 mayimpact throughput or latency of communications between a UE in pool 210and the remote cloud network 250 via the enterprise RAN and coreinfrastructure module 230. The ways in which each of these variablesimpacts quality of connection between the pool of UEs 210 and the remotecloud network 250 may vary over time as the applications executed bythese UEs in pool 210 changes, various UEs enter or leave the pool 210of linked UEs, the capabilities of the UEs within the pool 210 changes(e.g., 4G UEs 211 increase in volume or 5G UEs 212 decrease in volume),or the locations of various UEs within the pool 210 changes relative tothe enterprise RAN and core infrastructure module 230.

The MANO 236 in an embodiment may also gather connectivity metrics andrequirements, infrastructure component configurations, MEC resourcedistribution metrics from each of the 4G RAN 231, the 5G RAN 232, theWi-Fi AP 233, the 4G EPC 234, and the 5G network core 235 in order tooptimize overall connectivity between the user pool 210 and the remotecloud network 250 or MEC 238 resources in an embodiment. For example,the MANO 236 may gather from each of these enterprise mobile networkinfrastructure components (e.g., the 4G RAN 231, the 5G RAN 232, theWi-Fi AP 233, the 4G EPC 234, and the 5G network core 235) the RAN andcore network conditions describing, for example, guaranteed bitrates,number of network slices available, number of active bearers andwireless links established with the pool of UEs 210, processorutilization rates, and antenna and switch loads. The MANO 236 mayfurther gather RAN and MEC infrastructure component configurations fromthe MEC 238, including current and total processor and memoryavailability, and distribution of processing and memory resources of theMEC 238 made available to each of the 4G RAN 231, the 5G RAN 232, theWi-Fi AP 233, the 4G EPC 234, and the 5G network core 235.

The MANO 236 in an embodiment may assess the communication needs for apool 210 of enterprise-managed UEs wirelessly linked to an enterpriseRAN and core infrastructure module 230 operating a plurality of cellularand non-cellular RANs, APs, and network cores. Both the enterprise RANand core infrastructure module 230 and the pool 210 ofenterprise-managed UEs in various embodiments described herein may bemanaged by enterprise IT professionals via a Management andOrchestration Module (MANO) 236, which may operate in part at theenterprise RAN and core infrastructure module 230, and in part (e.g.,via intelligent wireless carrier link management system 214) at each ofthe UEs within the enterprise-managed pool 210 as well asremotely-located global management and orchestration in the cloud invarious embodiments. The MANO 236 in embodiments described herein mayoperate to perform adjustments predicted by the intelligent wirelesscarrier link management system 237 (e.g., as output from a neuralnetwork) to optimize ability of the enterprise network to meetconnectivity requirements of the pool 210 of enterprise-managed UEs.

The MANO 236 may orchestrate functionality of the 4G RAN 231, 4G EPC234, 5G RAN 232, 5G Core 235, Wi-Fi AP 233, and MEC resources 238 andassess the communication needs for the pool 210 of enterprise-managedUEs wirelessly linked to the enterprise RAN and core infrastructure 230.The MANO 236 may scale up or increase antenna systems or computingresources of various RANs (e.g., 231 or 232), APs (e.g. 233), or cores(e.g., 234 or 235) while scaling down or decreasing antenna systems orcomputing resources at other RANs (e.g., 231 or 232), APs (e.g. 233), orcores (e.g., 234 or 235) to increase the ability of the componentswithin the enterprise RAN and core infrastructure 230 to establishwireless links capable of satisfying connectivity requirements for thepool 210. Such scaling of the components within the enterprise RAN andcore infrastructure 230 may prompt the MANO 236 in embodiments of thepresent disclosure to increase, decrease, or reroute wireless links atone or more UEs in pool 210 communicating via the enterprise mobilenetwork in order to take advantage of the optimized scaling of variouscomponents within the enterprise RAN and core infrastructure 230.

The MANO 236 in an embodiment may also instruct UEs within pool 210 toestablish or alter wireless link parameters or antenna configuration toaccount for such infrastructure scaling. The MANO 236 facilitates this,for example, by adjusting policies for one or more of these UEs in pool210 as stored at the 4G EPC 234 (as described in greater detail withrespect to FIG. 3 ) or the 5G core 235 (as described in greater detailwith respect to FIG. 5 ). Wireless policy adjustments at the one or moreUEs in pool 210 may include selecting among subscriptions to access oneor more service provider radio access networks or may include policyadjustments that include selection among other available wireless radioaccess networks that may be subscription-based, enterprise managedprivate networks, or public wireless networks.

Such policies may be assigned to each UE by an IT professional of theenterprise operating the enterprise mobile network, and may beadjustable or dynamically adaptable based on real-time metricsdescribing the usage, location, or movement of the UE, or changes to theinfrastructure of the enterprise mobile network. For example, in anembodiment described with reference to FIG. 2 , in which the MANO 236increases capabilities at the 4G RAN 231, or 4G EPC 234, the MANO 236may also adjust a policy favoring or prioritizing 5G wireless links andfor one or more of the UEs in pool 210 to favor 4G wireless links, inorder to direct those UEs to communicate via the 4G RAN 231 and 4G EPC234. Those UEs may thus take advantage of the expanded capabilities atthose 4G components of the enterprise RAN and core infrastructure 230.As another example, in an embodiment in which the MANO 236 increasescapabilities at the 5G RAN 232, or 5G core 235, the MANO 236 may alsoadjust a policy favoring or prioritizing 4G wireless links for one ormore of the UEs in pool 210 to favor 5G wireless links, in order todirect those UEs to communicate via the 5G RAN 232 and 5G core 235.Those UEs may thus take advantage of the expanded capabilities at those5G components of the enterprise RAN and core infrastructure 230. Instill another example, in an embodiment in which the MANO 236 decreasescapabilities at the 4G RAN 231, or 5G RAN 232, the MANO 236 may alsoadjust a policy favoring or prioritizing cellular wireless links for oneor more of the UEs in pool 210 to favor or prioritize non-cellular(e.g., non-3GPP, Wi-Fi, Bluetooth®) wireless links, in order to directthose UEs to communicate via the Wi-Fi AP 233. Those UEs may thuscompensate for the diminished capabilities at the RAN components (e.g.,231 and 232) of the enterprise RAN and core infrastructure 230.

One or more of the UEs in pool 210 in an embodiment may also beassociated with an electronic subscriber identity module (eSIM) profilestored at a subscription manager data preparation platform 237 of theenterprise mobile network. Such eSIM profiles may be maintained by an ITprofessional of the enterprise mobile network and may be associated withor contain credentials unique to a single UE within pool 210 that can beused to identify one or more separate enterprise UE connectivityprofiles associated with that single UE describing intendedfunctionality of the UE at a given time and associated enterpriseprofile requirements. For example, such enterprise profile requirementsmay include a low-power profile in which the user intends to operate theUE under battery power, a travel profile in which the user intends tooperate the UE while in transit or located remotely from an enterprisecampus or other preferred location. As another example, such enterpriseprofile requirements may include one or more connectivity requirementsneeded to optimize performance of one or more software applicationscurrently executing or which the user intends to execute shortly at theUE. More specifically, such enterprise profile requirements may indicatea priority for wireless links optimized for high throughput, lowlatency, or high security, for example.

Each UE within pool 210 in an embodiment may operate an intelligentwireless carrier link management system 214 which may function to adjustantennas at individual UEs according to UE antenna configurationadjustments determined at the MANO 236 (e.g., as described in greaterdetail with respect to FIG. 8 ) or by the intelligent wireless carrierlink management system 214 itself, as described in greater detail withrespect to FIG. 7 . Such UE antenna configuration adjustments in variousembodiments described herein may be made based on changing operatingconditions (e.g., connectivity requirements and metrics) at one or moreof the UEs within pool 210, changes made to enterprise UE connectivityprofiles stored at the subscription manager data preparation platform237, or on changes in capacity at one or more enterprise RAN and coreinfrastructure 230 components (e.g., 4G RAN 231, 5G RAN 232, ornon-cellular AP 233) made by the MANO 236.

The ways in which connectivity metrics for wireless links 220established between the UE pool 210 and the enterprise RAN and coreinfrastructure 230 impacts quality of communications between the pool210 of UEs and the remote cloud network 250 or MEC metrics, as routedthrough various components of the enterprise RAN and core infrastructure230 may vary over time as the applications executed by these UEschanges, various UEs enter or leave the pool 210 of linked or managedUEs, the capabilities of the UEs within the pool 210 changes (e.g., more4G capable UEs 211 enter and more 5G capable UEs 212 exit), or thelocations of various UEs within the pool 210 changes. The MANO 236 in anembodiment addresses these issues by routinely assessing thecommunication needs for the pool 210 of UEs wirelessly linked to theenterprise RAN and core infrastructure 230 operating a plurality ofcellular and non-cellular RANs (e.g., 231 and 232), APs (e.g., 233), andnetwork cores (e.g., 234 and 235) and adjusting availability ofresources at each of these RANs, APs, and cores to meet UE needs.

For example, the MANO 236 in an embodiment may scale up computing orprocessing resources available at any of the 4G RAN 231, 5G RAN 232, 4GEPC 234, or 5G core 235 based on determination that a RAN or core isexperiencing congestion, high-latency, or low throughput. In such anembodiment, the MANO 236 may further work in tandem with the intelligentwireless carrier link management system 214 at one or more UEs in thepool 210 to take advantage of these scaled up computing or processingresources by transceiving at least a portion of data through therecently scaled up component of the enterprise RAN and coreinfrastructure 230. As another example, the MANO 236 in an embodimentmay increase the number of antennas transceiving data at the 4G RAN 231,5G RAN 232, or Wi-Fi AP 233 when one of these components of theenterprise RAN and core infrastructure 230 is experiencing high trafficload. In such an embodiment, the MANO 236 may further work in tandemwith the intelligent wireless carrier link management system 214 at oneor more UEs in the pool 210 to take advantage of these newly addedantennas by transceiving at least a portion of data through the recentlyactivated antennas.

The MANO 236 in an embodiment may also operate to redistribute wirelesslinks between a plurality of UEs in the pool 210 and variousinfrastructure components (e.g., 4G RAN 231, 5G RAN 232, non-cellular AP233, 4G EPC 234, or 5G core 235) of the enterprise RAN and coreinfrastructure 230 to ensure UE connectivity requirements are met for asmany UEs in pool 210 as possible. In such an embodiment, the MANO 236may do so, for example, by assigning one or more wireless links capableof meeting specific UEs connectivity requirements, as indicated byconnectivity metrics for those wireless links, to that specific UE. Morespecifically, the MANO 236 in such an example embodiment may assign awireless link with the 4G RAN 231, 5G RAN 232, or non-cellular AP 233having connectivity metrics indicating a high throughput to a UE withinpool 210 having a connectivity requirement for high throughput. Asanother example, the MANO 236 in such an example embodiment may assign awireless link with the 4G RAN 231, 5G RAN 232, or non-cellular AP 233having connectivity metrics indicating a low latency to a UE within pool210 having a connectivity requirement for low latency.

In some cases, UE connectivity requirements cannot be met for all UEs inthe pool 210. For example, the number of wireless links havingconnectivity metrics indicating high throughput may be less than thenumber of UEs in pool 210 that are requesting high throughput wirelesslinks. As another example, the number of wireless links havingconnectivity metrics indicating low latency may be less than the numberof UEs in pool 210 that are requesting low latency wireless links. Insuch scenarios, the MANO 236 may access Enterprise UE connectivityprofiles from the subscription manager data preparation platform 237 todetermine which UEs in pool 210 should be given priority for wirelesslinks in high demand. Such profiles may indicate a UE rank or prioritystatus, as assigned to the UE by an IT professional of the enterprise.For example, a UE assigned to a corporate officer of the enterprise maybe given a higher UE rank or priority status in comparison to a UEassigned to a new employee. As another example, a UE designated forprocessing large volumes of data central to the business operations ofthe enterprise may be given a highest UE rank or priority status. As yetanother example, a UE located within a certain geographical area such asa secure portion of an enterprise campus or a meeting room of anenterprise campus routinely used for sales or negotiations may be givena higher UE rank or priority status. These UE ranks or priority statusesmay be considered enterprise profile requirements in various embodimentsdescribed herein. By retrieving or accessing such enterprise UEconnectivity profiles stored at the subscription manager datapreparation platform 237 in an embodiment, the MANO 236 may assignwireless links in high demand to UEs in pool 210 indicating such ademand according to UE rank or priority status. For example, the MANO236 may assign high demand wireless links to all UEs in pool 210indicating such a demand in a highest UE rank or priority status first,then in descending order of UE rank or priority status until all highdemand wireless links have been distributed.

FIG. 3 is a block diagram illustrating a 4G Radio Access Network (RAN)360 and Evolved Packet Core (EPC) 350 of an enterprise mobile networkaccording to an embodiment of the present disclosure. As describedherein, user equipment devices (UEs), such as laptop/notebook computingdevices, desktop computing devices, tablet computing devices, mobilephones, or other endpoint computing devices often utilize wirelessnetworks in order to exchange data via a plurality of remote cloudnetworks 380. Such UEs may communicate via one or more wireless linksestablished between an antenna system of the UE and a 4G Radio AccessNetwork (RAN) 360 or non-cellular network access point (AP) 330, forexample. Large businesses or corporations may establish campuses inwhich employee UEs may establish wireless links to a remote cloudnetwork 380 via one or more business-operated enterprise mobilenetworks. Such enterprise mobile network may incorporate infrastructurefor establishing wireless links via a plurality of wirelesscommunications standards, such as, for example, 4G cellular, 5Gcellular, or non-cellular protocol such as Wi-Fi, or Bluetooth®. In suchcases, a single enterprise mobile network may establish wireless linkswith a pool 340 of UEs via one or more of a 4G RAN (e.g., 360), a 5GRAN, or a non-cellular wireless communication AP (e.g., 330). Further,communications received at each of the 4G RAN (e.g., 360), 5G RAN, andnon-cellular wireless communication AP (e.g., 330) may be routed to aremote cloud network 380 via either a 4G Evolved Packet Core (EPC)(e.g., 350) or a 5G core. FIG. 3 illustrates a 4G RAN 360 communicablylinked to a pool of UEs 340, a 5G gNodeB 390 of a 5G RAN, and a 4G EPC350 to establish wireless communications according to the 4G standardwith the pool of UEs 340.

The 4G RAN 360 comprises a plurality of computing nodes called eNodeBs(e.g., 361 or 370) that operate to transceive data with the user device(UE) pool 340 according to 4G wireless communication standards. EacheNodeB (e.g., 361 or 370) performs radio resource management tasks,mobility management functions, and performs any necessary encryptions ordecryptions on received data packets. For example, the eNodeB (e.g., 361or 370) may track where each of the pool of UEs 340 are located, manageco-channel interference, radio resources, and other radio transmissioncharacteristics such as transmit power, user allocation, beamforming,data rates, handover criteria, modulation schemes, and error codingschemes, to utilize the limited radio-frequency spectrum resources andradio network infrastructure as efficiently as possible.

An eNodeB (e.g., 361 or 370) may comprise at least one group of anantenna system, a Remote Radio Unit (RRU), and a Base Band Unit in anembodiment. For example, eNodeB 370 may incorporate a single antennasystem 371, a single RRU 372, and a single base band unit (BBU) 374 inan embodiment. As another example, eNodeB 361 in an embodiment mayincorporate one group of infrastructure including antenna system 362,RRU 363, and BBU 365, and another group of infrastructure includingantenna system 366, RRU 367, and BBU 369. The UE pool 340 in anembodiment may include one or more UEs capable of establishing wirelesslinks with the 4G RAN 360. In some embodiments, a single UE within thepool 340 may establish multiple wireless links with the 4G RAN 360. Forexample, a single UE within the pool 340 in an embodiment may establishone wireless link with antenna system 362 and another wireless link withantenna system 366. Similarly, each of the antenna systems (e.g., 362,366, and 371) may be capable of establishing wireless links with aplurality of UEs within the UE pool 340. The MANO 320 may increaseprocessing capacity at an eNodeB (e.g., 361 or 370) in an embodiment byincreasing the number of antennas transceiving data with the UE pool340, for example.

In an example embodiment, one or more UEs within pool 340 may establisha plurality of wireless links with an eNodeB 361 comprising a pluralityof antennas 362 and 366, a plurality of RRUs 363 and 367, and aplurality of BBUs 365 and 369. In such an embodiment, the antennasystems 362 and 366 may transceive data packets within electronic radiofrequency (RF) signals according to the 4G cellular standard. Uponreceipt of a such RF signals from the pool of UEs 340, the RRUs 363 and367 in such an embodiment may perform RF signal processing functionalitylike transmit and receive functions, filtering, amplification,analog-to-digital conversion, digital-to-analog conversion,up-conversion, and down-conversion on the received RF signals. In such away, each RRU (e.g., 363 and 367, or 372) in an embodiment may operateas network interface device capable of processing a maximum uplink loadaccording to an adjustable load setting.

Each of the RRUs 363 and 367 in such an embodiment may be connected toBBU 365 and BBU 369, respectively, via optical fibers 364 and 368,respectively. Each of these optical fibers 364 and 368 in an embodimentmay transceive data according to the common public radio interface(CPRI). The BBUs 365 and 369 may process uplink and downlink datatraffic and control functionality of the RRUs 363 and 367, respectively.For example, BBUs 365 and 369 may orchestrate uplink and downlinktraffic across antennas 362 and 366, respectively, during execution ofmultiple input multiple output (MIMO) transmissions. In such anembodiment, processing resources available to the single eNodeB 361 maybe consumed during execution of these functions of the plurality of RRUs363 and 367 and the plurality of BBUs 365 and 369. Each BBU (e.g., 365,369, or 374) in an embodiment may operate as a containerized softwareapplication. The number of BBUs executing at any given eNodeB (e.g., 361or 370), or across the entire 4G RAN 360 in an embodiment may bedictated by a preset BBU replication rate. The performance of the BBUs(e.g., 365, 369, or 374) in an embodiment may further be impacted by apreset processor call priority setting which dictates the priority withwhich a processor may execute calls from such BBUs. In other words, ahigher processor call priority setting may result in a BBU processing ahigher volume of data packets over a certain time period than anotherBBU with a lower processor call priority setting. Thus, the MANO 320 inan embodiment may increase processing capacity at an eNodeB (e.g., 361or 370) by increasing a BBU replication rate or associating a BBU with ahigher processor call priority setting, for example.

A UE within pool 340 in another example embodiment may establish awireless link with an eNodeB 370 comprising a single antenna 371, singleRRU 372, and single BBU 374. In such an embodiment, a UE within the pool340 may establish a wireless link with antenna system 371, for example.In such an embodiment, the antenna system 371 may transceive datapackets within a radio frequency band utilized under a 4G RAN protocol,the RRU 372 may receive these data packets via the antenna system 371,and the BBU 374 may receive data packets processed by the RRU 372 viaoptical fiber 373 transceiving data in CPRI format. Similarly, to theeNodeB 361 infrastructure described directly above, RRU 372 in such anembodiment may perform RF signal processing functionality, and BBU 374may process uplink and downlink data traffic and control RRU 372functionality. In such an embodiment, processing resources available tothe single eNodeB 370 may be consumed during execution of thesefunctions of the single RRU 372 and the single BBU 374.

In other words, in an embodiment in which eNodeB 361 and eNodeB 370 haveaccess to the same processing resources, fewer of those resources may bededicated to execution of functions by the RRUs 363 and 367 and BBUs 365and 369 than may be dedicated to execution of functions by the RRU 372and BBU 374. This may cause an increase in processing time, and thus anincrease in latency for transceiving of data packets through the eNodeB361 in comparison to transceiving of data packets through the eNodeB370, for example. However, placing two antennas 362 and 366 within asingle eNodeB 361 increases the volume of data packets that may betransceived via wireless links with eNodeB 361 during any given timeperiod (e.g., throughput of wireless links with eNodeB 361) incomparison to the throughput of wireless links established with eNodeB370. Thus, increasing the number of antenna systems (e.g., 362 and 366),RRUs (e.g., 363 and 367) and BBUs (e.g., 365 and 369) within a singleeNodeB (e.g., 361) in an embodiment may increase latency and throughput,while decreasing the number of antenna systems (e.g., 371), RRUs (e.g.,372), and BBUs (e.g., 374) within a single eNodeB (e.g., 370) maydecrease latency and throughput.

4G RAN 360 eNodeBs (e.g., 361 and 370) in an embodiment may obtainauthenticated access and authorized transceiving of packets andtransceive data packets for further processing to the 4G Evolved PacketCore 350. In other embodiments, the 4G RAN 360 may transmit data packetsfor further processing to a 5G core via an optical fiber 391 and 5Glogical 5G radio node (gNodeB) 390 of the 5G RAN, as described ingreater detail with respect to FIG. 5 below. In such a way, the eNodeB(e.g., 361 or 370) may function as a network switch to route databetween BBUs (e.g., 365, 369, or 374) and the 4G EPC 350 or the 5GgNodeB 390. Performing such network switch functionality, the eNodeB(e.g., 361 or 370) in such an embodiment may route a certain trafficload, and each eNodeB (e.g., 361 or 370) may be assigned an adjustablemaximum traffic load.

Some portions of the infrastructure within the 4G EPC 350 and itsfunctionality in an embodiment may be proprietary, and not scalable bythe enterprise. In contrast, as described in greater detail with respectto FIG. 5 , the 5G core may operate as a plurality of containerizedsoftware applications, many or all of which may be managed, scaled, andorchestrated by the MANO 320. In some embodiments, certain portions ofthe infrastructure within the 4G EPC 350 may be scalable, however,including the Serving Gateway (S-GW) 303, and the Packet Data NetworkGateway (P-GW) 305.

The eNodeB 370 in an embodiment may exchange messages with the mobilitymanagement entity (MME) 301 in an embodiment via an S1-MME interface 376adhering to the General Packet Radio Service Tunneling Protocol for theuser-plane (GTP-U). The MME 301 may communicate with the Home SubscriberServer (HSS) 312 via an S6A interface 319 to authenticate each of thepool of UEs 340. The HSS 312 in an embodiment may comprise a centraldatabase that contains user-related and subscription-related informationand UE policy information, as described in greater detail below. The MME301 may then perform tasks relating to activating and deactivatingwireless links with specifically identified (e.g., by eSIM) UEs withinpool 340, and authorizing access to one of a plurality of availableserving gateways (e.g., 303) to process data packets or data framesexchanged via wireless links with the pool of UEs 340.

Upon authorization and activation of one or more of the UEs in the pool340 via the MME 301 in an embodiment, the MME 301 may notify the servinggateway (S-GW) 303 that the UEs in pool 340 have been authenticated viaS11 interface 302. The S-GW 303 in an embodiment may receive user datapackets from the eNodeB (e.g., 370) via an S1-U interface 375, and routeand forward those user data packets to the Packet Data Network Gateway(P-GW) 305 via S5 connection 304. In such a way, the S-GW 303 mayfunction as a network switch to route data between BBUs (e.g., 365, 369,or 374) and the P-GW 305. Performing such network switch functionality,the S-GW 303 in such an embodiment may route a certain traffic load, andmay be assigned an adjustable maximum traffic load.

Transmission of data packets between the S-GW 303 and the P-GW 305 in anembodiment may be through a fiber-optic cable or bus using an S5interface, for example. The P-GW 305 in an embodiment providesconnectivity between the pool of UEs 340 and the remote cloud network380. Data packets received from the UEs 340 at the P-GW 305 in anembodiment may be encapsulated within IP packets for transmission to theremote cloud network 380. The P-GW 305 may transceive IP packets withthe remote cloud network 380 via a fiber-optic cable or bus using an SGiinterface 316. Headers for IP packets received at the P-GW 305 from theremote cloud network 380 may be stripped from encapsulated data packets,and the stripped data packets may be forwarded to the S-GW 303 fortransmission to UEs within the pool 340 via the eNodeB (e.g., 370). Insuch a way, the P-GW 305 may function as a network switch to route databetween S-GW 303 and a remote cloud network 380. Performing such networkswitch functionality, the P-GW 305 in such an embodiment may route acertain traffic load, and may be assigned an adjustable maximum trafficload.

The 4G EPC 350 in an embodiment may comprise a plurality of S-GWs (e.g.,303) and P-GWs (e.g., 305). Each S-GW (e.g., 303) and P-GW (e.g., 305)in an embodiment may operate as a containerized software application.The number of S-GWs (e.g., 303) and P-GWs (e.g., 305) executing at the4G EPC 350 in an embodiment may be dictated by a preset replicationrate. The performance of the S-GWs (e.g., 303) and P-GWs (e.g., 305) inan embodiment may further be impacted by a preset processor callpriority setting which dictates the priority with which a processor mayexecute calls from such S-GW (e.g., 303) and P-GW (e.g., 305). In otherwords, a higher processor call priority setting may result in an S-GW(e.g., 303) or P-GW (e.g., 305) processing a higher volume of datapackets over a certain time period than another S-GW (e.g., 303) or P-GW(e.g., 305) with a lower processor call priority setting. Thus, the MANO320 in an embodiment may increase processing capacity at the 4G EPC 350by increasing an S-GW or P-GW replication rate or associating an S-GW orP-GW with a higher processor call priority setting, for example.

Each BBU (e.g., 365, 369, or 374), S-GW 303, or P-GW 305 in anembodiment may be associated with various performance requirements. Inaddition, each eNodeB (e.g., 361 or 370), the entirety of the 4G RAN360, and the 4G EPC 350 may also be associated with performancerequirements. For example, each BBU (e.g., 365, 369, or 374), S-GW 303,or P-GW 305 in an embodiment may be associated with a maximum processorutilization rate capping the percentage of processing resourcesaccessible by that BBU (e.g., 365, 369, or 374), S-GW 303, or P-GW 305.As another example, the eNodeB (e.g., 361 or 370), the 4G RAN 360, andthe 4G EPC 350 may be associated with a guaranteed bit rate (GBR)defining a portion of network and processing resources set aside orreserved for executions of those systems. If the performance metrics forthe eNodeB (e.g., 361 or 370), the 4G RAN 360, and the 4G EPC 350 in anembodiment indicate any of those systems are not consuming the networkor processing resources set aside according to the GBR, this mayindicate an adjustment to the infrastructure component configuration maybe needed. In other words, this may indicate a need to adjust theprocessing resources allocated to the eNodeB (e.g., 361 or 370), the 4GRAN 360, or the 4G EPC 350, to adjust changes to the data connection toaccommodate the pool of UEs 340 seeking access.

The P-GW 305 in an embodiment may also perform enforcement of rulesgenerated by the policy/charging rules function (PCRF). The PCRF 307 inan embodiment may generate policy and charging rules containingcharging-related information and Quality of Service (QoS) parametersused in bearer establishment. These policies may inform or dictate thetypes of wireless communication networks with which each UE associatedwith a given policy may establish wireless connections, based on linkperformance requirements, security requirements, types of networkssupported by a given UE, or other factors in various embodiments. Thesepolicies may be transmitted to the P-GW via a fiber-optic cable or bususing an S-6A interface 318 from the HSS 312, then transmitted to thePCRF 307 via a fiber-optic cable or bus using a Gx interface 306, forexample.

The policies pursuant to which the PCRF 307 in an embodiment mayestablish the rules enforced by the P-GW 305 may be stored at the HSS312, with each UE within the pool 340 being associated with one or moreof such stored policies. For example, a single UE within the pool 340 inan embodiment may be associated with a policy stored at the HSS 312 thatspecifies the types of wireless communication networks (e.g., 3G, 4G,5G, Wi-Fi, Wi-Max, BlueTooth®, Near Field Communications (NFC), etc.)with which the UE associated with that policy may be capable ofestablishing wireless links depending on network conditions determinedby the MANO 320. As another example, such a policy may identify whethera given UE supports 5G network slicing capabilities. As yet anotherexample, such a policy may identify a given UE's preference of one typeof wireless communication network over another (e.g., preference ofcellular over Wi-Fi, preference of 5G over 4G, preference of Wi-Max overWi-Fi, etc.), or preference of one type of cellular network core overanother (e.g., preference of processing wireless signals through the 5Gcore rather than the 4G core). In yet another example, such a policy mayidentify one or more policy-based connectivity requirements. Morespecifically, a UE may be associated with a minimum thresholdrequirement for signal strength, throughput, latency, or other wirelessconnectivity metrics for establishing wireless links and may be utilizedby the MANO 320 to determine end to end data connection resources andenterprise mobile network infrastructure used and allocated to 4G RANand the EPC core.

In still another example, such a policy may identify one or moresecurity levels with which a given UE may be associated. Such securitylevels may be assigned to each UE by an IT professional of theenterprise operating the enterprise mobile network, and may beadjustable or dynamically adaptable based on real-time metricsdescribing the usage, location, or movement of the UE. For example, useof specific applications may cause the UE to be associated with a higherlevel of security needed to protect transmission of information pursuantto execution of such programs. As another example, location of the UE ona campus or a specific sub-portion of a campus for the enterprise maycause the UE to be associated with a higher level of security. As yetanother example, movement of the UE within the campus may indicate thedevice is mobile, and thus, less likely to require a higher level ofsecurity reserved for stationary desktop devices located within secureareas of the campus. In still other examples, the role of the UE usermay dictate the assigned security level, such that employees regularlyengaging in transfer of sensitive data (e.g., confidential technicalinformation, confidential legal or accounting information, etc.) may beassigned a higher security rating than an individual not regularlytransferring such data.

The P-GW 305 in an embodiment may also act as a gateway between the 4GEPC 350 and an access point transceiving data according to anon-cellular or non-3GPP standard, such as a WLAN or Bluetooth® network.For example, a UE within the pool 340 may establish a wireless link witha non-cellular access point 330, through which a GTP-U tunnel 317 to anevolved packet data gateway (ePDG) 311 of the 4G EPC 350 may beestablished. The ePDG 311 in such an embodiment may receive IP packetsfrom the pool of UEs 340 via this GTP-U tunnel 317. The ePDG 311 maycommunicate with the authorization, authentication, accounting module(AAA) 314 via a fiber-optic cable or bus using an SWm interface 315 toauthenticate the UE within the pool 340 with which the GTP-U tunnel 317has been established. The AAA may be in communication with the stored UEsubscriber information in the HSS 312 via a fiber-optic cable or bususing an SWx interface 313. Upon such an authentication, the ePDG 311may forward the received IP packets to the P-GW 305 via an IP sessiontunnel 310. As with data packets received via the eNodeB (e.g., 370) inan embodiment described directly above, the P-GW 305 may then transmitthese received IP packets to the remote cloud network 380 or MECresources via a fiber-optic cable or bus using the SGi interface 316.Similarly, the P-GW 305 may receive IP packets via the SGi interface 316from the remote cloud network 380, then forward those IP packets to theUE pool 340 via the ePDG 311 and the non-cellular AP 330. In such a way,a UE within the pool 340 may establish a wireless link to the 4G EPC 350(and ultimately to the remote cloud network 380 or MEC resources) viaeither the eNodeB of the 4G RAN or the non-cellular AP 330.

As described herein, the enterprise mobile network in an embodiment maybe managed by a single entity or enterprise, and may include a pluralityof RANs (e.g., 4G RAN 360, or 5G RAN described with reference to FIG. 4below), cellular network cores (e.g., 4G Evolved Packet Core 350, or 5Gcore described with reference to FIG. 5 below), and non-cellular accesspoints (e.g., WLAN or BlueTooth® AP 330). Each UE within pool 340 may becapable of establishing a wireless link with a RAN (e.g., 4G RAN 360, or5G RAN described with reference to FIG. 4 below), or a non-cellular AP(e.g., WLAN or BlueTooth® AP 330) in an embodiment. Wirelessconnectivity metrics for each wireless link may vary based on the typeof RAN or AP with which a UE has established such a link. For example, awireless link between a UE within pool 340 and 4G RAN 360 may providegreater throughput than a wireless link between that UE and the WLAN/BTAP 330, while the wireless link between that UE and the WLAN/BT AP 330provides lower latency. This is only one of many possible comparisonsbetween wireless connectivity metrics of wireless links establishedbetween a UE within pool 340 and any given RAN or AP in variousembodiments. Other connectivity metrics that may be considered forcomparison between two wireless links may include, for example, securityof the wireless link, signal strength, percentage of dropped packets, oranother wireless connectivity metric routinely monitored, recorded, orstored at a UE within pool 340, at the HSS 312, or at the MANO 320, asdescribed herein. Thus, choice of the RAN or AP through whichcommunications between a UE in the pool 340 and the remote cloud network380 or MEC resources may be routed may impact overall connectivitymetrics of such communications.

A 5G RAN may be capable of transceiving data with a 5G network core(e.g., as described with reference to FIGS. 4 and 5 below), while a 4GRAN (e.g., 360) may be capable of transceiving data with either a 4G EPC350 or a 5G core. For example, the 4G RAN 360 may transceive data with a5G gNodeB 390 within a 5G RAN via an X2 interface 391 in an embodiment.Further, a non-cellular AP (e.g., 330) may be capable of transceivingdata with a plurality of available cellular network cores (e.g., 4GEvolved Packet Core 350, or 5G core described with reference to FIG. 5below). Processing performed at any core (e.g., EPC 350 or a 5G coredescribed with reference to FIG. 5 below) may impact overallconnectivity metrics between a UE within pool 340 and the remote cloudnetwork 380 or MEC metrics. For example, high traffic, high processingutilization, or high rates of node failure at a given core may increaselatency, decrease throughput, or otherwise negatively impact the overallcommunication between such a UE within pool 340 and the remote cloudnetwork 380 or MEC metrics. As another example, routing ofcommunications between such a UE within pool 340 and the remote cloudnetwork 380 or MEC metrics through a specific network slice (e.g., asdescribed in greater detail with respect to FIG. 5 below) may increasethroughput, decrease latency, provide heightened security, or otherwisepositively impact the overall communication between such a UE withinpool 340 and the remote cloud network 380 or MEC metrics. Thus, choiceof cellular core through which communications between a UE in the pool340 and the remote cloud network 380 or MEC metrics may be routed mayimpact overall connectivity metrics of such communications.

The ways in which each of these connectivity metrics impacts quality ofcommunications between the pool 340 of UEs and the remote cloud network380 or MEC metrics, as routed through various components of theenterprise mobile network may vary over time as the applicationsexecuted by these UEs changes, various UEs enter or leave the pool 340of linked UEs, the capabilities of the UEs within the pool 340 changes(e.g., more 4G capable UEs enter and more 5G capable UEs exit), or thelocations of various UEs within the pool 340 changes. The MANO 320 in anembodiment addresses these issues by routinely assessing thecommunication needs for the pool 340 of UEs wirelessly linked to theenterprise mobile network operating a plurality of cellular andnon-cellular RANs (e.g., including 4G RAN 360), APs (e.g., including AP330), and network cores (e.g., including 4G EPC 350) and adjustingavailability of resources at each of these RANs, APs, and cores to meetUE needs.

For example, the MANO 320 in an embodiment may scale up computing orprocessing resources available at the 4G RAN 360 or 4G EPC 350experiencing congestion, high-latency, or low throughput. In such anembodiment, the MANO 320 may further work in tandem with the intelligentwireless carrier link management system at one or more UEs in the pool340 to take advantage of these scaled up computing or processingresources by transceiving at least a portion of data through therecently scaled up 4G RAN 360 or 4G EPC 350. As another example, theMANO 320 in an embodiment may increase the number of antennas (e.g.,362, 366, or 371) transceiving data at the 4G RAN 360 when the 4G RAN360 is experiencing high traffic load. In such an embodiment, the MANO320 may further work in tandem with the intelligent wireless carrierlink management system at one or more UEs in the pool 340 to takeadvantage of these newly added antennas by transceiving at least aportion of data through the recently activated antennas. As yet anotherexample, the MANO 320 in an embodiment may redirect traffic movingthrough the 4G RAN 360 to access the 4G EPC 350 via the non-cellular AP330, rather than through the 4G RAN 360 when one or more of the BBUs(e.g., 365, 369, or 370) are experiencing heavy traffic loads. In suchan embodiment, the MANO 320 may further work in tandem with theintelligent wireless carrier link management system at one or more UEsin the pool 340 to terminate wireless links established with the 4G RAN360 and establish wireless links to the 4G EPC 350 via the non-cellularAP 330.

The MANO 320 in an embodiment may also instruct one or more UEs in thepool 340 to adjust their antenna configurations in order to achieve theoptimal wireless link distribution determined at the MANO 320 anddescribed directly above. For example, the MANO 320 may instruct one ormore UEs in pool 340 currently transceiving data via a wireless linkbetween a first antenna at the UE and either the 5G RAN or non-cellularAP 330 to activate a second antenna for transceiving of data via awireless link to the 4G RAN 360. Similarly, the MANO 320 may instructone or more UEs in pool 340 currently transceiving data via a wirelesslink between a first antenna at the UE and the 4G RAN 360 to deactivatethis first antenna when the MANO 320 decreases computing or processingresources available at the 4G RAN 360. As another example, the MANO 320may instruct one or more UEs in pool 340 currently transceiving data viaa wireless link between a first antenna at the UE and either the 5G RANor non-cellular AP 330 to activate a second antenna for transceiving ofdata via a wireless link to these newly activated antennas at the 4G RAN360. Similarly, the MANO 320 may instruct one or more UEs in pool 340currently transceiving data via a wireless link between a first antennaat the UE and the 4G RAN 360 to deactivate this first antenna when theMANO 320 decreases the number of antennas available at the 4G RAN 360.In yet another example, the MANO 320 may instruct one or more UEs inpool 340 currently transceiving data via a wireless link between a firstantenna at the UE and the 4G RAN 360 to deactivate the first antenna andto activate a second antenna for transceiving of data via a wirelesslink to the non-cellular AP 330 in order to reroute traffic away from acongested 4G RAN 360.

FIG. 4 is a block diagram illustrating a 5G Radio Access Network (RAN)480 of an enterprise 5G communication system according to an embodimentof the present disclosure. Some or all components of the 5G RAN 480 maybe located at an enterprise mobile network (e.g., comparable to thatdiscussed directly above with respect to FIG. 3 ) in some embodiments.More specifically, the enterprise mobile network in an embodiment mayincorporate or access a cloud native RAN Intelligent Controller (RIC)441 operating to coordinate communication of data through a plurality oflogical 5G radio nodes (gNodeBs) (e.g., 450). In some embodiments, oneor more of such gNodeBs (e.g., 450) may be co-located with the RIC 441within the enterprise mobile network. In other embodiments, one or moreof such gNodeBs (e.g., 450) may be separated into one or more facilitiesseparate from the RIC 441, in accordance with the decentralizedarchitectural approach for which the 5G communication standard wasdesigned, as described in greater detail below.

As described herein, user equipment devices (UEs) within a pool 490 maycommunicate via one or more wireless links established by an antennasystem of the UE within the enterprise mobile network incorporatinginfrastructure for establishing wireless links via a plurality ofwireless communications standards, such as, for example, 4G cellular, 5Gcellular, or non-cellular protocol such as Wi-Fi, or Bluetooth®. In suchcases, a single enterprise mobile network may establish wireless linkswith a pool 490 of UEs via one or more of a 4G RAN (e.g., as describedwith reference to FIG. 3 above), a 5G RAN 480, or a non-cellularwireless communication AP (e.g., as described with reference to FIGS. 2and 4 ). Further, communications received at each of the 4G RAN, 5G RAN480, and non-cellular wireless communication AP may be routed to aremote cloud network 473 or local MEC resources via either a 4G EPC(e.g., as described with reference to FIG. 3 above) or a 5G core 470,with each core located within the enterprise mobile network. FIG. 4illustrates a 5G RAN 480 communicably linked to a pool of UEs 490, a 4GeNodeB 408 and a 5G core 470 to establish wireless communicationsaccording to the 5G standard with the pool of UEs 490.

The 5G communication standard categorizes a frequency spectrum toinclude low bands for a larger coverage area and lower performance, ahigh band for network densification through mmWave for a smallercoverage area but higher performance, and mid-band that providesmid-range coverage and mid-range performance. Frequency bands availablefor the establishment of wireless links to include frequencies below 1GHz and above 60 GHz (e.g., 5G mmWave). The higher bands supportfrequency bands to operate best within short distances between the UEpool 490 and the antenna system (e.g., 401, 402, or 405) with which awireless link has been established. In order to provide this high-bandcoverage within an area that is comparable to the larger area ofcoverage for 4G systems, 5G systems may use several antenna systems(e.g., 401, 402, or 405). This 5G strategy may provide more completehigh-band coverage (e.g., by placing a 5G antenna within an area withpoor connectivity to the 4G RAN), with greater bandwidth availabilitythan 4G (e.g., within the 5G mmWave frequencies). In order to make this5G solution economically feasible, 3GPP designed the 5G standard todecentralize the functionality of the RAN into various components thatmay or may not be co-located with one another, to decrease the size andcost of each 5G cell and to optimize the cost-per-bit for the transportlayer. This decentralization and movement of RAN components to aplurality of locations within a single cell results in the ability topush some computing overhead involved in transceiving of data packetsbetween the UE pool 490 and a remote cloud network 473 or MEC resourcesaway from the centralized RAN or core (e.g., as described in the 4G RAN360 of FIG. 3 ) and towards the “edge” of the network that include theantenna systems.

The 5G RAN 480 in an embodiment may comprise one or more logical 5Gradio nodes (gNodeBs) (e.g., 450). A single gNodeB in an embodiment maycomprise a logical architecture of several components, including a RadioUnit (RU) (e.g., 403 and 406), a Distributed Unit (DU) (e.g., 410 and412), and a Centralized Unit (CU) node (e.g., 430). Each of thesecomponents may be co-located with one another in a single physicalstructure, or located in separated locations, connected to one anothervia fiber optical cables, for example. The locations of each of thesecomponents with respect to one another may be a reflection of the degreeto which the 5G RAN 480 pushes processing overhead toward the edges ofthe network. For example, locating the RU (e.g., 403 and 406), DU (e.g.,410 and 412), and CU (e.g., 430) together may provide a centralizedarchitecture that pushes all overhead for gNodeB 450 to a singlephysical location (e.g., server rack or server farm). As anotherexample, locating the RU (e.g., 403 and 406), DU (e.g., 410 and 412),and CU (e.g., 430) each in separate facilities housing separate serverracks may provide a fully distributed architecture that pushes all RUand DU processing overhead to the outer edges of the network onto thecell site for superior network performance and high pooling gains.Although FIG. 4 depicts a single gNodeB 450, the 5G RAN 480 in otherembodiments may incorporate a plurality of gNodeBs.

The 5G RAN 480 in an embodiment may perform many of the same functionsof the 4G RAN described above with reference to FIG. 3 , but differsfrom the 4G RAN in that it decouples the functionality of the 4G RRU andthe 4G BBU to allow for the decentralization described directly above,as well as for optimized distribution of processing capacity across aplurality of gNodeBs (e.g., 450). UEs within pool 340 in an embodimentmay establish wireless links with Radio Units (e.g., 403 and 406) of the5G RAN 480. Each RU (e.g., 403 or 406) may be co-located with andservice one or more antenna systems (e.g., 401, 402, or 405). Forexample, RU 403 may service a plurality of antenna systems 401 and 402,while RU 406 services a single antenna system 405. The RUs (e.g., 403and 406) in an embodiment may comprise an RF transmitter and a LO PHYprocessing block for processing of the lower physical layer of cellulardata frames from the UE pool 490. In such a way, each RU (e.g., 403 or406) in an embodiment may operate as network interface device capable ofprocessing a maximum uplink load according to an adjustable loadsetting.

In an embodiment in which RU 403 services two antennas 401 and 402 andRUs 403 and 406 have access to the same processing resources, the amountof time required for RU 403 to perform this processing on signalstransceived via both antennas 401 and 402 may be greater than the amountof time required for RU 406 to perform this same processing on signalstransceived via antenna 405 alone. Thus, increasing the number ofantennas (e.g., 401 and 402) serviced by a single RU 403 in anembodiment may increase the latency of communication between the UE pool490 and a remote cloud network 473 or MEC resources. However, servicingtwo antennas (e.g., 401 and 402) via a single RU (e.g., 403) in anembodiment may increase the throughput of wireless links establishedwith RU 403. Because each RU (e.g., 403 and 406) in an embodiment mayservice a separate physical space, this may be preferable when demandfor wireless links within a given geographic area (e.g., density of UEswithin a 5G cell) increases.

Each RU (e.g., 403 or 406) may be in communication with a DistributedUnit (DU) (e.g., 410, or 412, respectively) via a fronthaul (e.g., 404or 407, respectively) interface. Each DU (e.g., 410 or 412) in anembodiment may comprise a HI PHY block for processing the higherphysical layer of cellular data frames received from the RU (e.g., 403or 406, respectively), a Media Access Control (MAC) block for processingthe MAC layer of the received cellular data frame, and a Radio LinkControl (RLC) block for processing the RLC layer of the receivedcellular data frame. The RUs (e.g., 403 or 406) may be co-located withthe DUs (e.g., 410 or 412) in some embodiments. In other embodiments,the DUs (e.g., 410 or 412) may be located in physically separatefacilities that are connected to the RUs (e.g., 403 or 406) via thefronthaul connections 404 and 407, respectively. Each DU (e.g., 410 or412) in an embodiment may operate as a containerized softwareapplication. The number of DUs (e.g., 410 or 412) executing at any givengNodeB (e.g., 450), or across the entire 5G RAN 480 in an embodiment maybe dictated by a preset DU replication rate. The performance of the DUs(e.g., 410 or 412) in an embodiment may further be impacted by a presetprocessor call priority setting which dictates the priority with which aprocessor may execute calls from such DUs. In other words, a higherprocessor call priority setting may result in a DU processing a highervolume of data packets over a certain time period than another DU with alower processor call priority setting. Thus, the MANO 474 in anembodiment may increase processing capacity at the DUs (e.g., 410 or412) by increasing a DU replication rate or associating the DUs (e.g.,410 or 412) with a higher processor call priority setting, for example.

All DUs (e.g., 410 and 412) within gNodeB 450 in an embodiment may be incommunication with a single centralized unit (CU) node 430 via an F1mid-haul connection (e.g., 411 and 413, respectively). In a split gNodeB450 embodiment, one or more of the DUs (e.g., 410 or 412) may be linkedto the CU node 430 in a separate physical location. The CU node 430 mayreceive IP packets from the DUs 410 and 412 and separate those packetsinto either control plane or user plane packets. As described above withrespect to FIG. 3 , the gNodeB 450 or the 5G RAN 480 may also receive IPpackets from an eNodeB 408 of a 4G RAN, to facilitate processing of the4G RAN originated IP packets via the 5G Core 470. In such an embodiment,the CU node 430 may receive IP packets from the 4G eNodeB 408 via an X2side-haul 409, and similarly separate those packets into either controlplane or user plane packets. In such a way, the DU 412 may function as anetwork switch to route data between the 4G eNodeB 408 of the 4G RAN andthe 5G core 470. Performing such network switch functionality, the DU412 in such an embodiment may route a certain traffic load, and each DU412 may be assigned an adjustable maximum traffic load.

The CU node 430 may comprise one or more centralized units (CUs) (e.g.,431 and 433) in an embodiment, primarily operating to split transceiveddata into a control plane and a user plane. The Control Plane CU (CU-C)433 in an embodiment may perform control plane functions in order tosuccessfully route and process data packets to the 5G core 470. Thesefunctions may include enforcing policies and protocols, identifyingpackets to be discarded, granting preferential treatment of certainpackets for which a high QoS is defined, establishing a user planesession, and ending a user plane session. The User Plane CU (CU-U) 431in an embodiment may perform user plane functions such as messagingbetween applications running at endpoints of the wireless communicationlinks (e.g., cloud-based applications within a remote cloud network 473or at MEC resources and UEs within pool 490) in order to facilitateexecution of these endpoint software applications. Separating thesefunctions into the user plane and the control plane may optimize theuser plane for simplicity, regularity, and speed of processinginter-application requests via transmission of data packets whileoptimizing the control plane for customizability and scalability. EachCU (e.g., 431 or 433) in an embodiment may operate as a containerizedsoftware application. The number of CUs (e.g., 431 or 433) executingacross the entire 5G RAN 480 in an embodiment may be dictated by apreset CU replication rate. The performance of the CUs (e.g., 431 or433) in an embodiment may further be impacted by a preset processor callpriority setting which dictates the priority with which a processor mayexecute calls from such CUs. In other words, a higher processor callpriority setting may result in a CU processing a higher volume of datapackets over a certain time period than another CU with a lowerprocessor call priority setting. Thus, the MANO 474 in an embodiment mayincrease processing capacity at the CUs (e.g., 431 or 433) by increasinga CU replication rate or associating the CUs (e.g., 431 or 433) with ahigher processor call priority setting, for example.

Each DU (e.g., 410, or 412) and CU (e.g., 431 or 433) in an embodimentmay be associated with various performance requirements. In addition,each gNodeB (e.g., 450), the entirety of the 5G RAN 480, and the 5G coremay also be associated with performance requirements. For example, eachDU (e.g., 410 or 412) and CU (e.g., 431 or 433) in an embodiment may beassociated with a maximum processor utilization rate capping thepercentage of processing resources accessible by that DU (e.g., 410 or412) or CU (e.g., 431 or 433). As another example, the gNodeB 450, 5GRAN 480, or 5G core 470 may be associated with a guaranteed bit rate(GBR) defining a portion of network and processing resources set asideor reserved for executions of those systems. If the performance metricsfor the gNodeB 450, 5G RAN 480, or 5G core 470 in an embodiment indicateany of those systems are not consuming the network or processingresources set aside according to the GBR, this may indicate anadjustment to the infrastructure component configuration may be needed.In other words, this may indicate a need to adjust the processingresources allocated to the gNodeB 450, 5G RAN 480, or 5G core 470.

The CU node 430 in an embodiment may service one or more DUs (e.g., 410and 412). As the number of DUs (e.g., 410 and 412) serviced by the CUnode 430 increases, the latency and throughput at such a CU node 430 mayalso increase. In contrast, as the number of DUs (e.g., 410 and 412)serviced by the CU node 430 decreases, latency and throughput at such aCU node 430 may also decrease. Thus, operations at each CU node (e.g.,430) within a 5G RAN 480 in an embodiment may be optimized for greaterthroughput or lower latency, dependent upon the needs of the pool of UEs490, by increasing or decreasing the number of DUs (e.g., 410 and 412)serviced by each CU node 430.

The 5G standard has been developed to allow for open-source softwaresolution performance of the various functions of the RU (e.g., 403 and406), DU (e.g., 410 and 412), and CU Node 430 on standardized hardwareconfigurations. Each of these open-source software solutions in anembodiment may operate as a containerized software application executingat one or more computing nodes. The enterprise mobile network in anembodiment may employ RIC node 440 to coordinate and optimize executionof each of the DU (e.g., 410 and 412) and CU node 430 functions. The RICnode 440 itself may operate as a containerized software application todistribute capacity across the plurality of DUs (e.g., 410 and 412), andCUs (e.g., including 430), while still meeting QoS requirements for UEsin pool 490. The 5G communication standard employs two different typesof RICs, including a near-real-time MC (MC near-RT) and a non-real-timeRIC (MC non-RT). The RIC near-RT may perform tasks that require onesecond or less latency, while the MC non-RT may perform tasks that areless latency-sensitive. The RIC near-RT may be co-located with the 5GRAN 480 (e.g., at MC node 440) in order to ensure low-latency processingof data received from the CU node 430. The RIC non-RT may be co-locatedwith the 5G RAN 480 and the RIC near-RT in some embodiments. In otherembodiments, the RIC non-RT may be located outside or remotely from the5G RAN 480, or may be co-located with infrastructure components of the5G core 470, for example. The RIC node 440 (e.g., incorporating the RICnear-RT) may communicate with the CU node 430 via an E2 Mid-haul 435,and with the DUs (e.g., 410 and 412) via an F1 Mid-haul (e.g., 414 and415, respectively).

5G RAN 480 gNodeBs (e.g., 450) in an embodiment may transceive datapackets for further processing to the 5G core 470. Upon separation ofdata by the CU Node 430 in an embodiment, data processed by the CU-U 431may be transmitted to the user plane function 472 of the 5G core 470,via an N3 backhaul connection 432 for establishment of a user session.Data processed by the CU-C 433 in an embodiment may be transmitted tothe Access and Mobility Management Function (AMF) 471 of the 5G core 470via an N2 backhaul connection 434 for execution of several networkfunctions at the 5G core 470, as described in greater detail below withrespect to FIG. 5 . In such a way, the CU-U 431 and CU-C 433 mayfunction as network switches to route data between the 5G RAN 480 andthe 5G core 470. Performing such network switch functionality, the CUs431 and 433 in such an embodiment may route a certain traffic load, andeach CU (e.g., 431 or 433) may be assigned an adjustable maximum trafficload.

As described herein, choice of the RAN or AP through whichcommunications between a UE in the pool 490 and the remote cloud network473 may be routed may impact overall connectivity metrics of suchcommunications. Further, the ways in which each of these connectivitymetrics impacts quality of communications between the pool 490 of UEsand the remote cloud network 473 or MEC resources, as routed throughvarious components of the enterprise mobile network (or portions ofgNodeB 450 or 5G RAN 480 located separately from the enterprise mobilenetwork) may vary over time as the applications executed by these UEschanges, various UEs enter or leave the pool 490 of linked UEs, thecapabilities of the UEs within the pool 490 changes (e.g., more 4Gcapable UEs enter and more 5G capable UEs exit), or the locations ofvarious UEs within the pool 490 changes. The MANO 474 in an embodimentaddresses these issues by routinely assessing the communication needsfor the pool 490 of UEs wirelessly communicating within the enterprisemobile network operating or transceiving data with a plurality ofcellular and non-cellular RANs (e.g., including at least some portionsof 5G RAN 480), APs, and network cores (e.g., including 5G core 470) andadjusting availability of resources at each of these RANs, APs, andcores to meet UE needs.

For example, the MANO 474 in an embodiment may scale up computing orprocessing resources available at the 5G RAN 480 or 5G core 470experiencing congestion, high-latency, or low throughput. In such anembodiment, the MANO 474 may further work in tandem with the intelligentwireless carrier link management system at one or more UEs in the pool490 to take advantage of these scaled up computing or processingresources by transceiving at least a portion of data through therecently scaled up 5G RAN 480 or 5G core 470. As another example, theMANO 474 in an embodiment may increase the number of antennas (e.g.,401, 402, or 450) transceiving data at the 5G RAN 480 when the 5G RAN480 is experiencing high traffic load. In such an embodiment, the MANO474 may further work in tandem with the intelligent wireless carrierlink management system at one or more UEs in the pool 490 to takeadvantage of these newly added antennas by transceiving at least aportion of data through the recently activated antennas. As yet anotherexample, the MANO 474 in an embodiment may redirect traffic movingthrough the 5G RAN 480 to access the 5G core 470 via a non-cellular AP(e.g., as described in greater detail with respect to FIG. 5 , below),rather than through the 5G RAN 480 when one or more of the DUs (e.g.,410 or 412) or CUs (e.g., 431, or 433) are experiencing heavy trafficloads. In such an embodiment, the MANO 474 may further work in tandemwith the intelligent wireless carrier link management system at one ormore UEs in the pool 490 to terminate wireless links established withthe 5G RAN 480 and establish wireless links to the 5G core 470 via anon-cellular AP (e.g., as described in greater detail with respect toFIG. 5 , below).

The MANO 474 in an embodiment may also instruct one or more UEs in thepool 490 to adjust their antenna configurations in order to achieve theoptimal wireless link distribution determined at the MANO 474 anddescribed directly above. For example, the MANO 474 may instruct one ormore UEs in pool 490 currently transceiving data via a wireless linkbetween a first antenna at the UE and either the 4G RAN or non-cellularAP to activate a second antenna for transceiving of data via a wirelesslink to the 5G RAN 480. Similarly, the MANO 474 may instruct one or moreUEs in pool 490 currently transceiving data via a wireless link betweena first antenna at the UE and the 5G RAN 480 to deactivate this firstantenna when the MANO 474 decreases computing or processing resourcesavailable at the 5G RAN 480. As another example, the MANO 474 mayinstruct one or more UEs in pool 490 currently transceiving data via awireless link between a first antenna at the UE and either the 4G RAN ornon-cellular AP to activate a second antenna for transceiving of datavia a wireless link to one of the newly activated antennas at the 5G RAN480. Similarly, the MANO 474 may instruct one or more UEs in pool 490currently transceiving data via a wireless link between a first antennaat the UE and the 5G RAN 480 to deactivate this first antenna when theMANO 474 decreases the number of antennas available at the 5G RAN 480.As yet another example, the MANO 474 may instruct one or more UEs inpool 490 currently transceiving data via a wireless link between a firstantenna at the UE and the 5G RAN 480 to deactivate the first antenna andto activate a second antenna for transceiving of data via a wirelesslink to the non-cellular AP.

FIG. 5 is a block diagram illustrating 5G network core of an enterprisemobile network according to an embodiment of the present disclosure. Asdescribed herein, choice of the cellular core through whichcommunications between a UE in the pool 590 and the remote cloud networkmay be routed may impact overall connectivity metrics of suchcommunications. FIG. 5 describes processing of data packets with a UEpool 590 via a 5G core 570 of the enterprise mobile network. Asdescribed herein, the 5G core 570 uses a service-based architecture, inwhich the 5G core processes data packets received from various RANs(e.g., gNodeB 550 of 5G RAN, or 4G eNodeB 408 in FIG. 4 ), ornon-cellular APs (e.g., 501) by executing a series of network functions(NFs), each operating as a separate containerized software application.These network functions comprise, at least, control plane services 510,subscriber management services 530, network resource management services540, and policy services 560. It is contemplated other networkfunctions, not illustrated within FIG. 5 may be incorporated within the5G core 570 described herein. Network functions are in communicationwith one another via fiber-optic cables or buses having point-to-pointreference points defining formatting of transceived messages between twoor more network functions. Each of these reference points may be definedwithin the 3GPP technical specifications (e.g., TS 23.501).

Because each of the NFs (e.g., 511, 512, 531, 532, 541, 542, 561, and562) within control plane services 510, subscriber management services530, network resource management services 540, and policy services 560are containerized software applications, the number of each NF executingwithin the 5G core 570 in an embodiment may be dictated by a preset NFreplication rate. The performance of the NFs in an embodiment mayfurther be impacted by a preset processor call priority setting whichdictates the priority with which a processor may execute calls from suchNFs. In other words, a higher processor call priority setting may resultin an NF processing a higher volume of data packets over a certain timeperiod than another NF with a lower processor call priority setting.

Each NF (e.g., 511, 512, 531, 532, 541, 542, 561, and 562) in anembodiment may be associated with various performance requirements. Inaddition, the 5G core 570 may also be associated with performancerequirements. For example, each NF in an embodiment may be associatedwith a maximum processor utilization rate capping the percentage ofprocessing resources accessible by that NF. As another example, the 5Gcore 570 may be associated with a guaranteed bit rate (GBR) defining aportion of network and processing resources set aside or reserved forexecutions of the 5G core 570. If the performance metrics for the 5Gcore 570 in an embodiment indicate the 5G core 570 is not consuming thenetwork or processing resources set aside according to the GBR, this mayindicate an adjustment to the infrastructure component configuration maybe needed. In other words, this may indicate a need to adjust theprocessing resources allocated to the 5G core 570.

The gNodeB 550 of the 5G RAN in an embodiment may exchange data packetswith the 5G core 570 via control plane and user plane. For example,control plane data may be transceived between a CU-C 551 of the gNodeB550 and an Access and Mobility Management Function (AMF) 511 of the 5Gcore 570 via an N2 backhaul connection 552. User plane data may also betransceived between a CU-U and a User Plane Function (UPF) of the 5Gcore, as described above with respect to FIG. 4 . The user plane andrelated functions within the 5G core are not the focus of FIG. 5 , andare thus not illustrated, although it is contemplated the 5G coredescribed with reference to FIG. 5 comprises such functionality.

The AMF 511 in an embodiment may operate as one of a plurality ofcontrol plane services 510 to oversee authentication, connection, andmobility management between the 5G core and each of the UEs in pool 590.Control plane services 510 in an embodiment may provide control of thenetwork, including access, mobility, policy, exposure, legal intercept,and charging related control. The Session Management Function (SMF) maybe included within the control plane services 510, which may operate tohandle session management, IP address allocation, and control of policyenforcement. The AMF may communicate with the SMF in an embodiment viaan N11 reference point connection 513, for example.

The SMF 512 in an embodiment may also facilitate direct communicationbetween a non-cellular AP 501 and the 5G core 570, eliminating the needto route communications to the 5G core 570 through the 5G RAN (e.g.,gNodeB 550). For example, one or more UEs in pool 590 may establish anIP Session Tunnel 502 with the non-cellular AP 501, which may, in turn,establish an IP Session Tunnel 503 to an N3 inter-working function 504of the enterprise mobile network. The N3 inter-working function 504 inan embodiment may transceive IP packets with the UE pool 590 via theseIP session tunnels 502 and 503, then transceive data packets with theSMF 512 via an N2 reference point connection 505.

The 5G core 570 may further include subscriber management services 530,including an authentication server function (AUSF) 531 and a UnifiedData Management (UDM) function 532. The AUSF 531 in an embodiment mayperform authentication with UEs within pool 490, similarly to the HSS ofthe 4G EPC. The AUSF 531 may be in communication with the AMF 511 via anN12 reference point connection 515, and with the UDM function 532 via anN13 reference point connection 533. The UDM function 532 in anembodiment may control access to a converged repository of subscriberinformation at the unified data repository (UDR) 506 from a plurality ofother NFs in the 5G core 570. The UDM function 532 may be incommunication in an embodiment with the SMF 512 via an N10 referencepoint connection 518, and with the AMF 511 via an N8 reference pointconnection 516.

The Unified Data Repository (UDR) 506 in an embodiment may store datarelating to connectivity metrics, connectivity requirements,infrastructure component configurations, and internetwork connectivityconfigurations. The UDR 506 may store policy information for theplurality of UEs, similar to that stored by the HSS of the 4G EPC. Thesepolicies may inform or dictate the types of wireless communicationnetworks with which each UE associated with a given policy may establishwireless connections, based on link performance requirements, securityrequirements, types of networks supported by a given UE, or otherfactors in various embodiments. For example, the UDR 506 may store aseparate policy for each of the UEs in the pool 590 that specifies thetypes of wireless communication networks (e.g., 3G, 4G, 5G, Wi-Fi,Wi-Max, BlueTooth®, Near Field Communications (NFC), etc.) with whichthe UE associated with that policy may be capable of establishingwireless links. As another example, such a policy may identify whether agiven UE supports 5G network slicing capabilities. As yet anotherexample, such a policy may identify a given UE's preference of one typeof wireless communication network over another (e.g., preference ofcellular over Wi-Fi, preference of 5G over 4G, preference of Wi-Max overWi-Fi, etc.), or preference of one type of cellular network core overanother (e.g., preference of processing wireless signals through the 5Gcore rather than the 4G core). In yet another example, such a policy mayidentify one or more policy-based connectivity requirements. Morespecifically, a UE may be associated with a minimum thresholdrequirement for signal strength, throughput, latency, or other wirelessconnectivity metrics for established wireless links.

In still another example, such a policy may identify one or moresecurity levels with which a given UE may be associated. Such securitylevels may be assigned to each UE by an IT professional of theenterprise operating the enterprise mobile network, and may beadjustable or dynamically adaptable based on real-time metricsdescribing the usage, location, or movement of the UE. For example, useof specific applications may cause the UE to be associated with a higherlevel of security needed to protect transmission of information pursuantto execution of such programs. As another example, location of the UE ona campus or a specific sub-portion of a campus for the enterprise maycause the UE to be associated with a higher level of security. As yetanother example, movement of the UE within the campus may indicate thedevice is mobile, and thus, less likely to require a higher level ofsecurity reserved for stationary desktop devices located within secureareas of the campus. In still other examples, the role of the UE usermay dictate the assigned security level, such that employees regularlyengaging in transfer of sensitive data (e.g., confidential technicalinformation, confidential legal or accounting information, etc.) may beassigned a higher security rating than an individual not regularlytransferring such data.

Network resource management services 540 may further be included withinthe 5G core 570 in an embodiment, including a network slice selectionfunction (NSSF) 541 and a network data analytics function (NWDA) 542.The NSSF 541 in an embodiment may select a network slice instancedefining specific versions or replicas of each network function to beused in concert with one another to process data packets transceivedwith one or more UEs in pool 590 that are assigned to a specificallyidentified network slice. The combination of each of these NF versionsor replicas may form a network slice in an embodiment, which may then beassigned by the NSSF 541 to one or more of such UEs in the pool 590. TheNSSF 541 may also operate in tandem with the AMF 511 via an N22reference point connection 543 to route traffic to the assigned networkslice. The NWDA 542 may access and transmit data stored at the UDR 506to the MANO 520 in an embodiment, upon request by the MANO 520.

The 5G core 570 may further include policy services 560, including acharging function (CHF) 561 and a policy control function (PCF) 562. TheCHF 561 in an embodiment may allow charging services to be offered toauthorized network functions, while the PCF 562 provides functionalitysimilar to the policy/charging rules function (PCRF) of the 4G EPC. Morespecifically, the PCF 562 in an embodiment may govern the networkbehavior by supporting a unified policy framework and accesssubscription or policy information for enforcement of policy decisions.The PCF 562 in an embodiment may be in communication with the AMF 511via an N15 reference point connection 514, and with the SMF 512 via anN7 reference point connection 519. The MANO 520 in an embodiment mayalso be capable of gathering any policies stored at the PCF 562.

As described herein, the enterprise mobile network in an embodiment maybe managed by a single entity or enterprise, and may include a pluralityof RANs (e.g., 4G RAN, or 5G RAN described with reference to FIGS. 2 and3 above), cellular network cores (e.g., 4G Evolved Packet Core describedwith reference to FIG. 3 above, or 5G core 570), and non-cellular accesspoints (e.g., WLAN or BlueTooth® AP 501). Each UE within pool 590 may becapable of establishing a wireless link with a RAN (e.g., 4G RANdescribed with reference to FIG. 3 , or 5G RAN described with referenceto FIG. 4 above), or a non-cellular AP (e.g., WLAN or BlueTooth® AP 501)in an embodiment. Wireless connectivity metrics for each wireless linkmay vary based on the type of RAN or AP with which a UE has establishedsuch a link. For example, a wireless link between a UE within pool 590and 4G RAN may provide greater throughput than a wireless link betweenthat UE and the WLAN/BT AP 501, while the wireless link between that UEand the WLAN/BT AP 501 provides lower latency. This is only one of manypossible comparisons between wireless connectivity metrics of wirelesslinks established between a UE within pool 590 and any given RAN or APin various embodiments. Other connectivity metrics that may beconsidered for comparison between two wireless links may include, forexample, security of the wireless link, signal strength, percentage ofdropped packets, or another wireless connectivity metric routinelymonitored, recorded, or stored at a UE within pool 590, at the UDR 506,at the MANO 520, as described herein. Thus, choice of the RAN or APthrough which communications between a UE in the pool 590 and the remotecloud network or MEC resources may be routed may impact overallconnectivity metrics of such communications.

Processing performed at any core (e.g., EPC 350 described with referenceto FIG. 3 , or 5G core 570) may impact overall connectivity metricsbetween a UE within pool 590 and the remote cloud network or MECresources. The ways in which each of these connectivity metrics impactsquality of communications between the pool 590 of UEs and the remotecloud network or MEC resources, as routed through various components ofthe enterprise mobile network may vary over time as the applicationsexecuted by these UEs changes, various UEs enter or leave the pool 590of linked UEs, the capabilities of the UEs within the pool 590 changes(e.g., more 4G capable UEs enter and more 5G capable UEs exit), or thelocations of various UEs within the pool 590 changes. The MANO 520 in anembodiment addresses these issues by routinely assessing thecommunication needs for the pool 590 of UEs wirelessly linked to theenterprise mobile network operating a plurality of cellular andnon-cellular RANs, APs (e.g., including AP 501), and network cores(e.g., including 5G core 570) and adjusting availability of resources ateach of these RANs, APs, and cores to meet UE needs. For example, theMANO 520 in an embodiment may operate to increase or decrease thecomputing resources dedicated to operation of various NFs (e.g., 511,512, 531, 532, 541, 542, 561, and 562) of the 5G core 570. Morespecifically, the MANO 520 may increase or decrease the replication rateor processor call priority setting for one or more NFs (e.g., 511, 512,531, 532, 541, 542, 561, and 562) to adjust the computing resourcesconsumed at the 5G core 570. As another example, the MANO 520 in anembodiment may redirect traffic moving through the 5G RAN 580 to accessthe 5G core 570 via the non-cellular AP 501, rather than through the 5GRAN 580 when one or more of the DUs or CUs of the 5G RAN 580 areexperiencing heavy traffic loads (e.g., as described above with respectto FIG. 4 ). In such an embodiment, the MANO 520 may further work intandem with the intelligent wireless carrier link management system atone or more UEs in the pool 590 to terminate wireless links establishedwith the 5G RAN 580 and establish wireless links to the 5G core 570 viathe non-cellular AP 501. The MANO 520 in such an embodiment may instructone or more UEs in pool 590 currently transceiving data via a wirelesslink between a first antenna at the UE and the 5G RAN 580 to deactivatethe first antenna and to activate a second antenna for transceiving ofdata via a wireless link to the non-cellular AP 501.

FIG. 6 is a block diagram illustrating an information handling system ofa user equipment device (UE) in wireless communication via a RAN or anAP of an enterprise mobile network according to an embodiment of thepresent disclosure. As described herein, the Management andOrchestration Module (MANO) in an embodiment may operate as a virtualmachine or containerized software application of a computing node withinthe enterprise mobile network in an embodiment to orchestrateavailability of computing resources for execution of various RANcomputing nodes and various services or network functions within a 5Gcore, to optimize communication for a pool of UEs, such as informationhandling system 600, communicating within the enterprise mobile network.In a networked deployment, the information handling system 600 mayoperate in the capacity of a server or as a client computer in aserver-client network environment, or as a peer computer system in apeer-to-peer (or distributed) network environment. In a particularembodiment, the computer system 600 can be implemented using electronicinformation handling systems that provide voice, video or datacommunication. For example, an information handling system 600 may beany mobile or other computing device capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that machine. Further, while a single information handling system 600is illustrated, the term “system” shall also be taken to include anycollection of systems or sub-systems that individually or jointlyexecute a set, or multiple sets, of instructions to perform one or morecomputer functions.

The information handling system can include memory (volatile (e.g.,random-access memory, etc.), nonvolatile (read-only memory, flash memoryetc.) or any combination thereof), one or more processing resources,such as a central processing unit (CPU), a graphics processing unit(GPU), hardware or software control logic, or any combination thereof.Additional components of the information handling system can include oneor more storage devices, one or more communications ports forcommunicating with external devices, as well as, various input andoutput (I/O) devices, such as a keyboard, a mouse, a video/graphicdisplay, or any combination thereof. The information handling system canalso include one or more buses operable to transmit communicationsbetween the various hardware components. Portions of an informationhandling system may themselves be considered information handlingsystems.

Information handling system 600 can include devices or modules thatembody one or more of the devices or execute instructions for the one ormore systems and modules described above, and operates to perform one ormore of the methods described above. The information handling system 600may execute code instructions 614 that may operate on servers orsystems, remote cloud networks, multi-access edge computing (MEC)systems, or on-box in individual client information handling systemsaccording to various embodiments herein. In some embodiments, it isunderstood any or all portions of code instructions 614 may operate on aplurality of information handling systems 600.

The information handling system 600 may include a processor 602 such asa central processing unit (CPU), control logic or some combination ofthe same. Any of the processing resources may operate to execute codethat is either firmware or software code. Moreover, the informationhandling system 600 can include memory such as main memory 604, staticmemory 606, computer readable medium 613 storing instructions 614 of anantenna selection algorithm, and drive unit 610 (volatile (e.g.,random-access memory, etc.), nonvolatile (read-only memory, flash memoryetc.) or any combination thereof). The information handling system 600can also include one or more buses 608 operable to transmitcommunications between the various hardware components such as anycombination of various input and output (I/O) devices.

As shown, the information handling system 600 may further include avideo display device 633. The video display device 633 in an embodimentmay function as a liquid crystal display (LCD), an organic lightemitting diode (OLED), a flat panel display, or a solid-state display.Additionally, the information handling system 600 may include an alphanumeric input device 634, such as a keyboard, and/or a cursor controldevice, such as a mouse, touchpad, or gesture or touch screen inputdevice. The information handling system 600 can also include a diskdrive unit 610.

The Wireless Wide Area Network (WWAN) interface device 650 may provideconnectivity of the information handling system 600 to a Radio AccessNetwork (RAN) 620, such as the 4G RAN described above in greater detailwith respect to FIG. 3 , or the 5G RAN described in greater detail abovewith respect to FIG. 4 , via one or more WWAN wireless links in anembodiment. The RAN 620, in combination with the 4G EPC (e.g., describedin greater detail with respect to FIG. 3 , above) or the 5G core (e.g.,as described in greater detail with respect to FIG. 5 , above) may forma WWAN communication network in an embodiment, which may comprise awired wide area network (WAN), a private LTE communication network, a 4GLTE public communication network, or a 5G millimeter-wave (mm-wave)communication network, or other cellular communication networks.Connectivity of the information handling system 600 of a UE device toany of a plurality of WWAN networks in an embodiment may be via wired orwireless connection. In some aspects of the present disclosure, the WWANinterface device 650 may operate two or more wireless links. In otheraspects of the present disclosure, the information handling system 600may include a plurality of WWAN interface devices, each operatingseparate radio subsystems.

The WWAN interface device 650 may operate in accordance with anycellular wireless data communication standards. WWAN interface device650, in an embodiment, may connect to any combination of macro-cellularwireless connections including 2G, 2.5G, 3G, 4G, 5G or the like from oneor more service providers. Utilization of radiofrequency communicationbands according to several example embodiments of the present disclosuremay include bands used with the WWAN standards, which may operate inboth licensed and unlicensed spectrums. More specifically, the WWANinterface device 650 in an embodiment may transceive within radiofrequencies associated with the 5G New Radio (NR) Frequency Range 1(FR1) or Frequency Range 2 (FR2). NRFR1 may include radio frequenciesbelow 6 GHz, associated with 4G LTE and other standards predating the 5Gcommunications standards now emerging. NRFR2 may include radiofrequencies above 6 GHz, made available within the now emerging 5Gcommunications standard. Communications within NRFR1 may be enabledthrough the use of either an evolved Node B (eNodeB) of a 4G RAN (asdescribed in greater detail with respect to FIG. 3 ) in combination withthe 4G EPC, or the 5G network core (as described in greater detail withrespect to FIG. 5 ), or a logical 5G radio node (gNodeB) of the 5G RAN(as described in greater detail with respect to FIG. 4 ), in combinationwith the 5G network core.

Frequencies related to the 5G networks may include high frequency (HF)band, very high frequency (VHF) band, ultra-high frequency (VHF) band, Lband, S band, C band, X band, Ku band, K band, Ka band, V band, W band,and millimeter wave bands. WWAN may use the Unlicensed NationalInformation Infrastructure (U-NII) band which typically operates in the˜5 GHz frequency band such as 802.11 a/h/j/n/ac (e.g., centerfrequencies between 5.170-5.785 GHz). It is understood that any numberof available channels may be available under the 5 GHz sharedcommunication frequency band. WWAN may operate in a number of bands,some of which are proprietary but may include a wireless communicationfrequency band at approximately 2.5 GHz band for example. In additionalexamples, WWAN carrier bands may operate at frequency bands ofapproximately 700 MHz, 800 MHz, 1900 MHz, or 1700/2100 MHz for exampleas well.

In an embodiment, the WWAN interface device 650 may be communicativelycoupled to an array of WWAN antenna systems 653 used to provide acommunication channel to one or more of the RANs (e.g., 620). The WWANantennas 653 may support a 5G wireless communication protocol so thatrelatively higher amounts of data may be transceived by the informationhandling system 600 to any WWAN communication network to which theinformation handling system 600 is communicatively coupled in someembodiments.

As described herein, the intelligent wireless carrier link managementsystem of an enterprise mobile network in an embodiment may work intandem with the MANO (e.g., as described in greater detail with respectto FIGS. 2-4 ) to increase or decrease the resources dedicated tooperation of antennas for any given cellular or non-cellular protocol.As the resources are increased or decreased at various RANs 620 or APs621 in such an embodiment, the UE information handling system 100 may bedirected to terminate wireless links with scaled-down networks andestablish new wireless links with scaled-up networks. The intelligentwireless carrier link management system 612 may receive suchinstructions from the MANO of an enterprise mobile network (e.g., asdescribed in greater detail with respect to FIGS. 2-4 ), viacommunication with the RAN 620, or the AP 621, for example. Theintelligent wireless carrier link management system 612 in such anembodiment may then instruct the WWAN radio subsystem 651 and the WWANantenna system 653 to establish the wireless links identified within thereceived instructions.

The WWAN antenna controller 652 may monitor wireless link stateinformation, wireless link configuration data, network slice data, orother input data to generate channel estimation and determine antennaradiation patterns. For example, the antenna controller 652 in anembodiment may receive, process, or store beacon data from an enterprisemobile network describing channels available for communication with theRAN 620, as well as various current traffic metrics for communicationson those channels. More specifically, such beacon information mayprovide a relative signal strength indicator (RSSI), identification ofthe communication channels as private or public, identification of theRAN 620 as compatible with multiple user, multiple input, multipleoutput (MU-MIMO) communications, high available data rate, levels ofchannel contention, and current load of communications at the RAN 620.Such beacon data may include such measurements or indications for eachof the channels within which the RAN 620 is capable of transceivingdata, and the beacons may be received in regular intervals.

The WWAN interface device 650 in an embodiment may further include aWWAN radio subsystem 651 which may operate to modulate and demodulatesignals transceived within a WWAN format, set signal transmission powerlevels or sensitivity to signal reception, select channels or frequencybands, and conduct other functions in support of a wireless transmissionfrom the pool of UEs 117 to 4G EPC 150 or the 5G network core 170.

The UE information handling system 600 in an embodiment may also becapable of establishing wireless links within an enterprise mobilenetwork via a non-cellular access point (AP) 621, vi a WLAN interfacedevice 660. The non-cellular AP 621 in an embodiment may routecommunications received from the information handling system 600 to the4G network core (e.g., as described with reference to FIG. 3 ), or the5G network core (e.g., as described with reference to FIG. 5 ). Thenon-cellular AP 621 may thus provide a WLAN network that may be a wiredlocal area network (LAN), a wireless personal area network (WPAN), apublic WiFi communication network, a private Wi-Fi communicationnetwork, a public WiMAX communication network, a Bluetooth®communication network, or any other non-cellular (non-3GPP)communication networks.

In some aspects of the present disclosure, the WLAN network interfacedevice 140 may operate two or more wireless links. In other aspects ofthe present disclosure, the information handling system 600 may includea plurality of WLAN network interface devices 660, each capable ofestablishing a separate wireless link to AP 621, such that theinformation handling system 600 may be in communication with AP 621, viaa plurality of wireless links.

The WLAN network interface device 660 may operate in accordance with anycellular wireless data communication standards. To communicate with awireless local area network, standards including IEEE 802.11 WLANstandards, IEEE 802.15 WPAN standards, WiMAX, Bluetooth®, or similarwireless standards may be used. Utilization of radiofrequencycommunication bands according to several example embodiments of thepresent disclosure may include bands used with the WLAN standards whichmay operate in both licensed and unlicensed spectrums. For example, WLANmay use the Unlicensed National Information Infrastructure (U-NII) bandwhich typically operates in the ˜5 MHz frequency band such as 802.11a/h/j/n/ac (e.g., center frequencies between 5.170-5.785 GHz). It isunderstood that any number of available channels may be available underthe 5 GHz shared communication frequency band. WLAN, for example, mayalso operate at a 2.4 GHz band, or a 60 GHz band.

In an embodiment, the WLAN network interface device 660 may becommunicatively coupled to an array of antenna systems 663 used toprovide a plurality of separate communication channels. As describedherein, the intelligent wireless carrier link management system of anenterprise mobile network in an embodiment may work in tandem with theMANO (e.g., as described in greater detail with respect to FIGS. 2-4 )to increase or decrease the resources dedicated to operation of antennasfor any given cellular or non-cellular protocol. As the resources areincreased or decreased at various RANs 620 or APs 621 in such anembodiment, the UE information handling system 100 may be directed toterminate wireless links with scaled-down networks and establish newwireless links with scaled-up networks. The intelligent wireless carrierlink management system 612 may receive such instructions from the MANOof an enterprise mobile network (e.g., as described in greater detailwith respect to FIGS. 2-4 ), via communication with the RAN 620, or theAP 621, for example. The intelligent wireless carrier link managementsystem 612 in such an embodiment may then instruct the WLAN radiosubsystem 661 and the WLAN antenna system 663 to establish the wirelesslinks identified within the received instructions.

The WLAN antenna controller 662 may monitor wireless link stateinformation, wireless link configuration data, network slice data, orother input data to generate channel estimation and determine antennaradiation patterns. For example, the WLAN antenna controller 662 in anembodiment may receive, process, or store beacon data from an enterprisemobile network describing channels available for communication with theAP 621, as well as various current traffic metrics for communications onthose channels. More specifically, such beacon information may provide arelative signal strength indicator (RSSI), identification of thecommunication channels as private or public, identification of the AP621 as compatible with multiple user, multiple input, multiple output(MU-MIMO) communications, high available data rate, levels of channelcontention, and current load of communications at the AP 621. Suchbeacon data may include such measurements or indications for each of thechannels within which the AP 621 is capable of transceiving data, andthe beacons may be received in regular intervals.

The WLAN network interface device 660 in an embodiment may furtherinclude a radio subsystem 661 which may operate to modulate anddemodulate signals transceived within a WLAN format, set signaltransmission power levels or sensitivity to signal reception, selectchannels or frequency bands, and conduct other functions in support of awireless transmission to the RAN 620 or the AP 621 of the enterprisemobile network.

The information handling system 600 may further include a softwaredefined networking (SDN) controller 640 operating to route packets orframes transceived pursuant to execution of certain softwareapplications via the OS 635 through specifically identified interfacedevices (e.g., WWAN interface device 650 or WLAN interface device 660).In another aspect of an embodiment, the SDN controller 640 may instructtransceiving of such packets or frames within specifically identifiedfrequency bands (e.g., below 1 MHz, between 1 MHz and 60 GHz, or above60 GHz). The SDN controller 640 in an embodiment may operate in acontrol plane layer (e.g., via software), in part, to route incomingpackets/frames to a network interface device for transmission in aspecific network slice. The SDN controller 640 in an embodiment mayinclude, for example, an OpenDaylight® controller, a NiciraNetworks/VMWare NOX™ controller, an NTT®/Google ONIX® controller, theNEC® Trema® controller, the NTT® Ryu® controller, or open-sourcedcontrollers such as PDX or Beacon controllers. In some embodiments, theSDN controller 160 may comprise a software-defined wide-area network(SD-WAN) controller operating to unify networking connections covering awide geographical area within an enterprise.

As illustrated, the WWAN interface device 650 in an embodiment mayinclude a local profile assistant (LPA) 655. The LPA 655 may include anenterprise UE connectivity profile associated with the UE informationhandling system 600. The enterprise UE connectivity profile may includean integrated circuit card identification number (ICCID) for the UEinformation handling system 600, an international mobile subscriberidentity (IMSI) number for the UE information handling system 600,security authentication and ciphering information for the UE informationhandling system 600, temporary information related to a local networkassociated with the UE information handling system 600, a list of theservices that the UE information handling system 600 has access to, andtwo passwords: a personal identification number (PIN) for ordinary use,and a personal unblocking key (PUK) for PIN unlocking. The enterprise UEconnectivity profile may further include enterprise profilerequirements, including a prioritized QoS requirement, prioritized powerconsumption, or prioritized security requirement, for example.

Examples of enterprise UE connectivity profiles prioritizing QoSrequirements may include a high-throughput enterprise profilerequirement that prioritizes establishment of wireless links thatprovide a high throughput, a low-latency enterprise profile requirementthat prioritizes establishment of wireless links that provide a lowlatency, or a hybrid enterprise profile requirement that directs theestablishment of one wireless link for throughput-dependentcommunications and a second, separate wireless link forlatency-dependent communications. An example of an enterprise UEconnectivity profile prioritizing power consumption may provide a powercap enterprise profile requirement under which all antennas (e.g., 653or 663) must operate while transceiving data, preference for wirelesslinks that do not require Virtual Private Network (VPN) tunnels, or anenterprise profile requirement that prioritizes power consumption at anyantenna (e.g., 653 or 663) of the UE 600 over consideration of QoSrequirements above a minimum threshold. Yet another example of anenterprise profile requirement may prioritize security requirements andmay require communication via a VPN tunnel or via a secure wireless linkwith 4G or 5G network cores, or may instruct transceiving of sensitivedata via a first antenna (e.g., 653 or 663) and transceiving of othernon-sensitive data via a second antenna (e.g., 653 or 663).

Users may choose from these enterprise UE connectivity profiles in someembodiments in order to inform current usage of the UE 600. For example,the enterprise UE connectivity profiles described directly above may bedisplayed to the user via a graphical user interface (GUI) 670. Bychoosing a specific profile, the user may indicate, for example, thatthe UE 600 should operate in low power mode (e.g., if the user plans tooperate the UE 600 on battery power for an extended period), highthroughput mode (e.g., if the user plans to transceive large volumes ofdata), low latency mode (e.g., if the user plans to executelatency-sensitive applications), or high security mode (e.g., if theuser plans to transceive sensitive data). The user may select from oneof the list of enterprise UE connectivity profiles displayed via GUI670, that may be presented to a user via video display 633.

As described herein, wireless link antenna configuration adjustments inan embodiment may also be determined by a Management and OrchestrationModule (MANO) in communication with the UE 600 via RAN 620, or via anout-of-band (00B) communication with the embedded controller 636. Suchdeterminations may be made, in various embodiments described herein, inorder to leverage changes in capacity at various infrastructurecomponents of the RANs (e.g., 620), non-cellular APs (e.g., 621), andcores comprising the enterprise mobile network, as made by the MANO, tooptimize performance across each of these infrastructure components andthe pool of UEs (e.g., including 600) communicating within the network.

Each of the UEs (e.g., including 600) in a pool may communicateconnectivity metrics for each of the UEs (e.g., including 600) withinthe pool to the MANO located at the enterprise mobile network managed bythe enterprise. For example, such connectivity metrics may includethroughput, latency, or other quality of service requirements for eachUE based on current wireless conditions at available wireless links,executing applications, and other operational data relating to thecurrent operating conditions of the UEs. Further, the enterprise mayestablish several enterprise profile requirements outlining securitypolicies associated with a UE 600 indicating a level of securityrequired for communication of data pursuant to execution of specificallyidentified software applications, or a level of security required forcommunication of data from specific geographic locations (e.g., within ageofenced area of an enterprise campus). As another example, suchconnectivity metrics may include identification of software applicationscurrently executed by an Operating System 635 of the UE 600, powermetrics describing current, previous, or projected power consumptionrates, and current power available (e.g., as stored at battery 637, oravailable via the A/C adapter 638). Connectivity metrics in anembodiment for the UE information handling system 600 in an embodimentmay include measurements of various quality of service (QoS) variablesfor established or available wireless links with the RAN 620 or thenon-cellular AP 621, including, for example, latency, throughput,dropped packets, security levels (e.g., Virtualized Private Network(VPN) tunnels), or network slice designations. These connectivitymetrics may further identify the antenna configurations (e.g., WLAN orWWAN, frequency band, gain, range, power requirements, etc.) throughwhich those wireless links have been established. Connectivityrequirements for the UE information handling system 600 in an embodimentmay describe QoS requirements UE 600, as defined by policies orenterprise UE connectivity profiles associated with the UE 600, storedin memory 604 or 606 and accessible via the embedded controller 636, invarious embodiments. Thus, the connectivity requirements for the UEinformation handling system 600 may be determined by the intelligentwireless carrier link management system 612 locally or remotely at theMANO based at least in part on currently executing softwareapplications, the connectivity metrics, policies stored at variouscellular network cores, and enterprise UE connectivity profiles managedby a subscription manager data preparation platform.

The intelligent wireless carrier link management system 612 may initiateor facilitate any wireless link antenna configuration adjustmentsdetermined by system 612 or received from the MANO via RAN 620 orembedded controller 636 in an embodiment, For example, in an embodimenta user or enterprise administrator may select an enterprise UEconnectivity profile that prioritizes throughput (or the system 612determines an antenna configuration prioritizing throughput is otherwiseappropriate) and may depend on currently executing softwareapplications, the intelligent wireless carrier link management system612 in an embodiment may direct establishment of a wireless link betweenthe WWAN interface device 650 and a RAN 620 or a wireless link betweenthe WLAN interface device 660 and a non-cellular AP 621 generatingbeacon data indicating the highest available throughput, but also basedon network intelligence data from the MANO or priority and connectivityrequirements data of other UEs in the pool of UEs. As another example,if the user selects an enterprise UE connectivity profile thatprioritizes latency (or the system 612 determines an antennaconfiguration minimizes latency is otherwise appropriate), theintelligent wireless carrier link management system 612 in an embodimentmay direct establishment of a wireless link between the WWAN interfacedevice 650 and a RAN 620 or a wireless link between the WLAN interfacedevice 660 and a non-cellular AP 621 generating beacon data indicatingthe lowest available latency, but also based on network intelligencedata from the MANO or priority and connectivity requirements data ofother UEs in the pool of UEs. As yet another example, if the userselects an enterprise UE connectivity profile that prioritizes security(or the system 612 determines an antenna configuration prioritizingsecurity is otherwise appropriate), the intelligent wireless carrierlink management system 612 in an embodiment may direct establishment ofa wireless link within a secure network slice of the 5G core via the RAN620, or a wireless link with a non-cellular AP 621 using a VPN tunnel,but also based on network intelligence data from the MANO or priorityand connectivity requirements data of other UEs in the pool of UEs.

The information handling system 600 may further include a powermanagement unit (PMU) 632 (a.k.a. a power supply unit (PSU)). The PMU632 may manage the power provided to the components of the informationhandling system 600 such as the processor 602, a cooling system, one ormore drive units 610, a graphical processing unit (GPU), a video/graphicdisplay device or other input/output devices 634, and other componentsthat may require power when a power button has been actuated by a user.In an embodiment, the PMU 632 may monitor power levels and beelectrically coupled to the information handling system 600 to providethis power and coupled to bus 608 to provide or receive data orinstructions. The PMU 632 may regulate power from a power source such asa battery 637 or A/C power adapter 638. In an embodiment, the battery637 may be charged via the A/C power adapter 638 and provide power tothe components of the information handling system 600 when A/C powerfrom the A/C power adapter 638 is removed.

Information handling system 600 includes one or more of an operatingsystem (OS) 635, and basic input/output system (BIOS) firmware/softwareor application programs that may be executable instructions 614 executedat any processor 602 and stored at one or more memory devices 604, 606,or 610. BIOS firmware/software functions to initialize informationhandling system 600 on power up, to launch an OS 635, and to manageinput and output interactions between the OS 635 and the other elementsof information handling system 600. In a particular embodiment, BIOSfirmware/software resides in memory 604, and include machine-executablecode that is executed by processor 602 to perform various functions ofinformation handling system 600 as described herein. In anotherembodiment (not illustrated), application programs and BIOSfirmware/software reside in another storage medium of informationhandling system 600. For example, application programs and BIOSfirmware/software can reside in drive 610, in a ROM (not illustrated)associated with information handling system 600, in an option-ROM (notillustrated) associated with various devices of information handlingsystem 600, in a storage system (not illustrated) associated withnetwork channel of a WWAN interface device 650 or a WLAN interfacedevice 660, in another storage medium of information handling system600, or a combination thereof. Executable code instructions 614 forapplication programs and BIOS firmware/software can each be implementedas single programs, or as separate programs carrying out the variousfeatures as described herein.

As shown in FIG. 6 , the information handling system 600 may furtherinclude an embedded subscriber identification module (eSIM) 654. TheeSIM 654 may include an integrated circuit card identification number(ICCID) for the information handling system 600, an international mobilesubscriber identity (IMSI) number for the information handling system600, security authentication and ciphering information for theinformation handling system 600, temporary information related to alocal network associated with the information handling system 600, alist of the services that the information handling system 600 has accessto, and two passwords: a personal identification number (PIN) forordinary use, and a personal unblocking key (PUK) for PIN unlocking.

In some embodiments, software, firmware, dedicated hardwareimplementations such as application specific integrated circuits,programmable logic arrays and other hardware information handlingsystems can be constructed to implement one or more of the methodsdescribed herein. Applications that may include the apparatus andsystems of various embodiments can broadly include a variety ofelectronic and computer systems. One or more embodiments describedherein may implement functions using two or more specific interconnectedhardware modules or information handling systems with related controland data signals that can be communicated between and through themodules, or as portions of an application-specific integrated circuit.Accordingly, the present system encompasses software, firmware, andhardware implementations.

In accordance with various embodiments of the present disclosure, themethods described herein may be implemented by firmware or softwareprograms executable by a controller such as embedded controller (EC) 636or a processor 602 system. Further, in an exemplary, non-limitedembodiment, implementations can include distributed processing,component/object distributed processing, and parallel processing.Alternatively, virtual computer system processing can be constructed toimplement one or more of the methods or functionalities as describedherein.

The present disclosure contemplates a computer-readable medium thatincludes instructions, parameters, and profiles 614 or receives andexecutes instructions, parameters, and profiles 614 responsive to apropagated signal; so that a device connected to a network via RAN 620or AP 621, for example, can communicate voice, video or data over thewireless network. Further, the instructions 614 may be transmitted orreceived over the wireless network via the network interface device(e.g., 650 or 660).

The information handling system 600 can include a set of instructions614 that can be executed to cause the computer system to perform any oneor more of the methods or computer-based functions disclosed herein. Forexample, instructions 614 may execute an antenna selection algorithm,various software applications, software agents, or other aspects orcomponents. Various software modules comprising application instructions614 may be coordinated by an operating system (OS), and/or via anapplication programming interface (API). An example operating system mayinclude Windows®, Android®, and other OS types known in the art. ExampleAPIs may include Win 32, Core Java API, or Android APIs.

The disk drive unit 610 and may include a computer-readable medium 613in which one or more sets of instructions 614 such as software can beembedded to be executed by the processor 602 to perform the processesdescribed herein. Similarly, main memory 604 and static memory 606 mayalso contain a computer-readable medium for storage of one or more setsof instructions, parameters, or profiles 614. The disk drive unit 610 orstatic memory 606 also contain space for data storage. Further, theinstructions 614 may embody one or more of the methods or logic asdescribed herein. In a particular embodiment, the instructions,parameters, and profiles 614 may reside completely, or at leastpartially, within the main memory 604, the static memory 606, and/orwithin the disk drive 610 during execution by the processor 602 ofinformation handling system 600. The main memory 604 and the processor602 also may include computer-readable media.

Main memory 604 or other memory of the embodiments described herein maycontain computer-readable medium (not shown), such as RAM in an exampleembodiment. An example of main memory 604 includes random access memory(RAM) such as static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM(NV-RAM), or the like, read only memory (ROM), another type of memory,or a combination thereof. Static memory 606 may containcomputer-readable medium (not shown), such as NOR or NAND flash memoryin some example embodiments. While the computer-readable medium is shownto be a single medium, the term “computer-readable medium” includes asingle medium or multiple media, such as a centralized or distributeddatabase, and/or associated caches and servers that store one or moresets of instructions. The term “computer-readable medium” shall alsoinclude any medium that is capable of storing, encoding, or carrying aset of instructions for execution by a processor or that cause acomputer system to perform any one or more of the methods or operationsdisclosed herein.

In a particular non-limiting, exemplary embodiment, thecomputer-readable medium can include a solid-state memory such as amemory card or other package that houses one or more non-volatileread-only memories. Further, the computer-readable medium can be arandom-access memory or other volatile re-writable memory. Additionally,the computer-readable medium can include a magneto-optical or opticalmedium, such as a disk or tapes or other storage device to storeinformation received via carrier wave signals such as a signalcommunicated over a transmission medium. Furthermore, a computerreadable medium can store information received from distributed networkresources such as from a cloud-based environment. A digital fileattachment to an e-mail or other self-contained information archive orset of archives may be considered a distribution medium that isequivalent to a tangible storage medium. Accordingly, the disclosure isconsidered to include any one or more of a computer-readable medium or adistribution medium and other equivalents and successor media, in whichdata or instructions may be stored.

In other embodiments, dedicated hardware implementations such asapplication specific integrated circuits, programmable logic arrays andother hardware devices can be constructed to implement one or more ofthe methods described herein. Applications that may include theapparatus and systems of various embodiments can broadly include avariety of electronic and computer systems. One or more embodimentsdescribed herein may implement functions using two or more specificinterconnected hardware modules or devices with related control and datasignals that can be communicated between and through the modules, or asportions of an application-specific integrated circuit. Accordingly, thepresent system encompasses software, firmware, and hardwareimplementations.

When referred to as a “system”, a “device,” a “module,” a “controller,”or the like, the embodiments described herein can be configured ashardware. For example, a portion of an information handling systemdevice may be hardware such as, for example, an integrated circuit (suchas an Application Specific Integrated Circuit (ASIC), a FieldProgrammable Gate Array (FPGA), a structured ASIC, or a device embeddedon a larger chip), a card (such as a Peripheral Component Interface(PCI) card, a PCI-express card, a Personal Computer Memory CardInternational Association (PCMCIA) card, or other such expansion card),or a system (such as a motherboard, a system-on-a-chip (SoC), or astand-alone device). The system, device, controller, or module caninclude software, including firmware embedded at a device, such as anIntel® Core class processor, ARM® brand processors, Qualcomm® Snapdragonprocessors, or other processors and chipsets, or other such devices, orsoftware capable of operating a relevant environment of the informationhandling system. The system, device, controller, or module can alsoinclude a combination of the foregoing examples of hardware or software.Note that an information handling system can include an integratedcircuit or a board-level product having portions thereof that can alsobe any combination of hardware and software. Devices, modules,resources, controllers, or programs that are in communication with oneanother need not be in continuous communication with each other, unlessexpressly specified otherwise. In addition, devices, modules, resources,controllers, or programs that are in communication with one another cancommunicate directly or indirectly through one or more intermediaries.

FIG. 7 is a flow diagram illustrating a method of determining a userequipment (UE) device antenna configuration adjustment, based onmetrics, requirements and policies for the UE according to an embodimentof the present disclosure. As described herein, the ways in whichvarious connectivity metrics impact quality of communications between apool of UEs and a remote cloud network or MEC resources, as routedthrough various components of the enterprise mobile network, may varyover time as the applications executed by these UEs changes, various UEsenter or leave the pool of linked UEs, the capabilities of the UEswithin the pool changes (e.g., more 4G capable UEs enter and more 5Gcapable UEs exit), or the locations of various UEs within the poolchanges. The intelligent wireless carrier link management system in anembodiment addresses these issues by routinely assessing thecommunication needs for each UE wirelessly linked within the enterprisemobile network, and determining when each UE would benefit from anincrease, decrease, or rerouting of wireless links established betweenthat UE and a remote cloud network via an enterprise mobile network.

A Management and Orchestration Module (MANO) of the enterprise mobilenetwork in various embodiments described herein may thus determine anoptimal distribution of wireless links having varying connectivitymetrics across a pool or UEs in communication via the enterprise mobilenetwork in order to meet connectivity requirements at a largest numberof those UEs to optimize connectivity among the linked or managed UEs.For example, the MANO in an embodiment may distribute or reroutewireless links across the pool of UEs in order to take advantage ofrecent scaling of processing resources at various infrastructurecomponents (e.g., RANs, non-cellular APs, MEC, or cellular networkcores) within the enterprise mobile network. As another example, theMANO may distribute or reroute wireless links across the pool of UEs toredirect traffic away from certain infrastructure components of theenterprise mobile network experiencing high traffic or congestion. Asyet another example, the MANO may distribute or reroute wireless linksacross the pool of UEs as the connectivity requirements for those UEschange over time (e.g., requirements for high throughput or lowlatency).

At block 702, a UE device executing the intelligent wireless carrierlink management system may be powered on. For example, in an embodimentdescribed with reference to FIG. 6 , the UE information handling system600 may power on when the power management unit 632 receives power viathe battery 637 or the A/C adapter 638. The power management unit 632may then power on the WWAN interface device 650.

A UE eSIM module or the MANO may retrieve a plurality of enterprise UEconnectivity profiles for the UE from a subscription manager datapreparation platform in an embodiment at block 704. For example, in anembodiment described with reference to FIG. 2 , 4G UE 211, 5G UE 212, orWiFi UE 213 may retrieve such enterprise UE connectivity profilesassociated with those UEs, respectively, from the subscription managerdata preparation platform 237 within the enterprise RAN and coreinfrastructure 230. In other embodiments, the subscription manager datapreparation platform 237 may be located within the remote cloud network250.

As another example, in an embodiment described with reference to FIG. 6, the eUICC 654 eSIM module operating at the UE information handlingsystem 600 in an embodiment may retrieve the plurality of enterprise UEconnectivity profiles for the UE 600 via the RAN 620. As illustrated,the WWAN interface device 650 in an embodiment may include a localprofile assistant (LPA) 655. The LPA 655 may include an enterprise UEconnectivity profile associated with the UE information handling system600. The enterprise UE connectivity profile may indicate a prioritizedQoS requirement, prioritized power consumption, or prioritized securityrequirement, for example.

Examples of enterprise UE connectivity profiles prioritizing QoSrequirements may include a high-throughput enterprise profilerequirement that prioritizes establishment of wireless links thatprovide a high throughput, a low-latency enterprise profile requirementthat prioritizes establishment of wireless links that provide a lowlatency, or a hybrid enterprise profile requirement that directs theestablishment of one wireless link for throughput-dependentcommunications and a second, separate wireless link forlatency-dependent communications. An example of an enterprise UEconnectivity profile prioritizing power consumption may provide a powercap enterprise profile requirement under which all antennas (e.g., 653or 663) must operate while transceiving data, preference for wirelesslinks that do not require Virtual Private Network (VPN) tunnels, orprioritization of power consumption at any antenna (e.g., 653 or 663) ofthe UE 600 over consideration of QoS requirements above a minimumthreshold. Yet another example of an enterprise profile requirement mayprioritize security requirements and may require communication via a VPNtunnel or via a secure wireless link with 4G or 5G network cores, or mayinstruct transceiving of sensitive data via a first antenna (e.g., 653or 663) and transceiving of other non-sensitive data via a secondantenna (e.g., 653 or 663).

At block 706, a graphical user interface (GUI) of the UE may display theplurality of retrieved enterprise UE connectivity profiles for the UEfor selection by the user. Users may choose from the enterprise UEconnectivity profiles retrieved at block 704 in some embodiments inorder to inform current usage of the UE 600. For example, the enterpriseUE connectivity profiles described directly above may be displayed tothe user via a graphical user interface (GUI) 670. By choosing aspecific enterprise UE connectivity profile, the user may indicate, forexample, that the UE 600 should operate according to a low powerenterprise profile requirement (e.g., if the user plans to operate theUE 600 on battery power for an extended period), high throughputenterprise profile requirement (e.g., if the user plans to transceivelarge volumes of data), low latency enterprise profile requirement(e.g., if the user plans to execute latency-sensitive applications),hybrid throughput/latency, or high security enterprise profilerequirement (e.g., if the user plans to transceive sensitive data).

At block 708, the intelligent wireless carrier link management systemmay direct the establishment of a wireless link in compliance with theuser-selected enterprise UE connectivity profile and correspondingenterprise profile requirement. For example, in an embodiment describedwith reference to FIG. 6 , the user may select from one of the list ofenterprise UE connectivity profiles displayed via GUI 670. As describeddirectly above, the user-selected enterprise UE connectivity profile mayindicate a highest priority requirement for a wireless link. Forexample, if the user selects an enterprise UE connectivity profilecontaining an enterprise profile requirement that prioritizesthroughput, the intelligent wireless carrier link management system 612in an embodiment may direct establishment of a wireless link between theWWAN interface device 650 and a RAN 620 or a wireless link between theWLAN interface device 660 and a non-cellular AP 621 generating beacondata indicating the highest available throughput. As another example, ifthe user selects an enterprise UE connectivity profile that prioritizeslatency, the intelligent wireless carrier link management system 612 inan embodiment may direct establishment of a wireless link between theWWAN interface device 650 and a RAN 620 or a wireless link between theWLAN interface device 660 and a non-cellular AP 621 generating beacondata indicating the lowest available latency. As yet another example, ifthe user selects an enterprise UE connectivity profile that prioritizessecurity, the intelligent wireless carrier link management system 612 inan embodiment may direct establishment of a wireless link within asecure network slice of the 5G core via the RAN 620, or a wireless linkwith a non-cellular AP 621 using a VPN tunnel.

In some embodiments, the intelligent wireless carrier link managementsystem may direct the establishment of a plurality of wireless links incompliance with the user-selected enterprise UE connectivity profile andassociated enterprise profile requirement. For example, if the userselects an enterprise UE connectivity profile that prioritizes both highthroughput and low latency (e.g., a hybrid profile), the intelligentwireless carrier link management system 612 may direct establishment ofa first wireless link, via a first antenna, between the WWAN interfacedevice 650 and a RAN 620 or a wireless link between the WLAN interfacedevice 660 and a non-cellular AP 621 generating beacon data indicatingthe lowest available latency and establishment of a second wirelesslink, via a second antenna, between the WWAN interface device 650 and aRAN 620 or a wireless link between the WLAN interface device 660 and anon-cellular AP 621 generating beacon data indicating the highestavailable throughput.

The intelligent wireless carrier link management system in an embodimentmay gather and transmit to the MANO UE connectivity metrics describingexecuting software applications and potential data bandwidth needs ofthose applications at block 710. In an example embodiment described withreference to FIG. 6 , each of the UEs (e.g., including 600) in pool mayexecute the intelligent wireless carrier link management system 612 tocommunicate connectivity metrics for each of the UEs (e.g., including600) within pool to the MANO located at the enterprise mobile networkmanaged by the enterprise. As an example, such connectivity metrics mayinclude identification of software applications currently executed by anOperating System 635 of the UE 600, projected data bandwidth needs ofthe software applications of the UE, of level of security required forcommunication of data pursuant to execution of specifically identifiedsoftware applications, or a level of security required for communicationof data from specific geographic locations of the UE (e.g., within ageofenced area of an enterprise campus). Additional connectivity metricsmay include power metrics describing current, previous, or projectedpower consumption rates, and current power available (e.g., as stored atbattery 637, or available via the A/C adapter 638).

Connectivity metrics in an embodiment for the UE information handlingsystem 600 in an embodiment may also include measurements of variousquality of service (QoS) variables for established wireless links withthe RAN 620 or the non-cellular AP 621, including, for example, latency,throughput, dropped packets, security levels (e.g., Virtualized PrivateNetwork (VPN) tunnels), or network slice designations gathered at block712. Connectivity requirements for the UE information handling system600 in an embodiment may describe QoS requirements UE 600, as defined bypolicies associated with the UE 600, stored in memory 604 or 606 andaccessible via the embedded controller 636, or as determined by theintelligent wireless carrier link management system 612 based oncurrently executing software applications. The UE 600 in an embodimentmay transmit these gathered connectivity metrics and any UE connectivityrequirements if determined at the UE, to the MANO of the enterprisemobile network in an embodiment, via an established wireless link withthe RAN 620, or the non-cellular AP 621, or via an out-of-bandcommunication occurring directly between the MANO and the embeddedcontroller 636, for example.

At block 712, the intelligent wireless carrier link management system inan embodiment may gather and transmit to the MANO UE connectivitymetrics describing QoS for all available wireless links as well asconnectivity metrics gathered at block 710 relating to executingsoftware applications and operation of the UE. For example, in anembodiment described with reference to FIG. 1 , the antenna controller142 in an embodiment may generate beacon data for transmission to one ormore of the pool of UEs 117 describing channels available forcommunication with that AP 190, as well as various current trafficmetrics for communications on those channels to determine QoS ofavailable wireless links. More specifically, such beacon information mayprovide a relative signal strength indicator (RSSI), identification ofthe communication channels as private or public, identification of theAP 190 as compatible with multiple user, multiple input, multiple output(MU-MIMO) communications, high available data rate, levels of channelcontention, and current load of communications at the AP 190. Suchbeacon data may include such measurements or indications for each of thechannels within which the AP 190 is capable of transceiving data, andthe beacons may be received in regular intervals.

In another example embodiment described with reference to FIG. 6 , theUE WWAN antenna controller 652 may receive, process, or store beacondata from an enterprise mobile network via WWAN radio 651 describingchannels available for communication with the RAN 620, as well asvarious current traffic metrics for communications on those channels.More specifically, such beacon information may provide a relative signalstrength indicator (RSSI), identification of the communication channelsas private or public, identification of the RAN 620 as compatible withmultiple user, multiple input, multiple output (MU-MIMO) communications,high available data rate, levels of channel contention, and current loadof communications at the RAN 620. Such beacon data may include suchmeasurements or indications for each of the channels within which theRAN 620 is capable of transceiving data, and the beacons may be receivedin regular intervals.

In still another example, the WLAN antenna controller 662 in anembodiment may receive, process, or store beacon data from AP 621, viaWLAN radio 661, describing channels available for communication with theAP 621, as well as various current traffic metrics for communications onthose channels. More specifically, such beacon information may provide arelative signal strength indicator (RSSI), identification of thecommunication channels as private or public, identification of the AP621 as compatible with multiple user, multiple input, multiple output(MU-MIMO) communications, high available data rate, levels of channelcontention, and current load of communications at the AP 621. Suchbeacon data may include such measurements or indications for each of thechannels within which the AP 621 is capable of transceiving data, andthe beacons may be received in regular intervals. Changes to these UEconnectivity metrics may trigger the intelligent wireless carrier linkmanagement system at the UE to analyze whether establishment of newwireless links at that UE or termination of existing wireless links arenecessary, as described in greater detail herein at block 716. The UE600 in an embodiment may transmit these gathered connectivity metrics(and connectivity requirements, if determined at the UE) to the MANO ofthe enterprise mobile network in an embodiment, via an establishedwireless link with the RAN 620, or the non-cellular AP 621, or via anout-of-band communication occurring directly between the MANO and theembedded controller 636, for example.

The MANO or the intelligent wireless carrier link management system inan embodiment may gather UE policies from network cores and enterpriseUE connectivity profiles from a subscription management data preparationplatform describing minimum QoS requirements and security requirementsat block 714. UE policies may be managed and stored at various cellularnetwork cores (e.g., 4G EPC or 5G core). For example, in an embodimentdescribed with reference to FIG. 3 , the HSS 312 of the 4G EPC 350 maystore policy information for the plurality of UEs in pool 340. As yetanother example, in an embodiment described with reference to FIG. 5 ,the UDR 506 of the 5G core 570 may store policy information for theplurality of UEs in pool 590. These policies may inform or dictate thetypes of wireless communication networks with which each UE associatedwith a given policy may establish wireless connections, based on linkperformance requirements, security requirements, types of networkssupported by a given UE, or other factors in various embodiments. Forexample, the UDR 506 or HSS 312 may store a separate policy for each ofthe UEs in the pool (e.g., 590 or 340, respectively) that identifies oneor more security levels with which a given UE may be associated. Suchsecurity levels may be assigned to each UE by an IT professional of theenterprise operating the enterprise mobile network, and may beadjustable or dynamically adaptable based on real-time metricsdescribing the usage, location, or movement of the UE or based ondetermined security levels of data for executing software applications.Changes to these UE policies at a UE may trigger the intelligentwireless carrier link management system at the UE to analyze whetherestablishment of new wireless links at that UE or termination ofexisting wireless links are necessary, as described in greater detailherein at block 716.

In an embodiment described with reference to FIG. 3 , for example, theMANO 320 may retrieve these policies describing minimum throughputvalues, maximum latency values, or other Quality of Service (QoS)requirements and security settings for a UE directly from the PCRF 307.In an embodiment described with reference to FIG. 5 , these minimumthroughput values, maximum latency values, or other Quality of Service(QoS) requirements, and security settings for such a UE, as storedwithin policies at the UDR 506 may be retrieved by the MANO 530 from thePCF 562. In another example embodiment described with respect to FIG. 6, policies associated with the UE 600 may be stored in memory 604 or 606and accessible to the MANO via the embedded controller 636.

Enterprise UE connectivity profiles may be managed by an IT manager ofthe enterprise via a subscription manager data preparation platform. TheMANO may retrieve enterprise UE connectivity profiles from thesubscription manager data preparation platform in an embodiment. Suchprofiles may indicate a UE rank or priority status, as assigned to theUE by an IT professional of the enterprise. For example, a UE assignedto a corporate officer or a key engineering or technical employee of theenterprise may be given a higher UE rank or priority status incomparison to a UE assigned to a new employee or an employee with lowercritical needs for bandwidth or low latency, or a UE with currentlyunused connectivity requirements. As another example, a UE designatedfor processing large volumes of data central to the business operationsof the enterprise may be given a highest UE rank or priority status. Asyet another example, a UE located within a certain geographical areasuch as a secure portion of an enterprise campus or a meeting room of anenterprise campus routinely used for sales or negotiations may be givena higher UE rank or priority status. As described in greater detail atblock 716 below, the MANO in an embodiment may refer to these UE ranksor priority statuses while determining the optimal wireless linkdistribution across all UEs, by assigning wireless links withconnectivity metrics that are in high demand based on UE rank orpriority status.

At block 716, the MANO or the intelligent wireless carrier linkmanagement system at the UE may determine whether currently establishedwireless links (e.g., as established at block 708) provide UEconnectivity metrics (e.g., as gathered at block 712) that meet UEconnectivity requirements determined based on UE connectivity metrics,enterprise profile requirements (e.g., within enterprise UE connectivityprofiles), and UE policies gathered at blocks 710, 712, and 714. TheMANO in an embodiment may determine connectivity requirements for a poolof UEs in communication via the enterprise mobile network, based on UEconnectivity metrics gathered from each of the individual UEs, UEpolicies gathered from network cores, enterprise profile requirementsgathered from the subscription manager data preparation platform, and ondetermined network conditions of various infrastructure components(e.g., RANs, non-cellular APs, or cellular cores) of the enterprisemobile network. For example, the MANO in an embodiment may determine aconnectivity requirement for high throughput is required for a UE basedon execution of a software application requiring high throughput (e.g.,as shown in connectivity metrics gathered at block 710), or based on anenterprise profile requirement for a high throughput wireless linkassociated with that UE (e.g., as shown in connectivity metrics gatheredat block 714). As another example, the MANO in an embodiment maydetermine a connectivity requirement for low latency is required for aUE based on execution of a software application requiring low latency(e.g., as shown in connectivity metrics gathered at block 710), or basedon an enterprise profile requirement for a low latency wireless linkassociated with that UE (e.g., as shown in connectivity metrics gatheredat block 714). As yet another example, the MANO in an embodiment maydetermine a connectivity requirement for a secure wireless link isrequired for a UE based on execution of a software application requiringsecure communication (e.g., as shown in connectivity metrics gathered atblock 710), or based on an enterprise profile requirement for a securewireless link associated with that UE (e.g., as shown in connectivitymetrics gathered at block 714). In other embodiments, determination ofconnectivity requirements may be made at individual UEs and transmittedto the MANO, rather than determined at the MANO, as described at block710, above.

As described herein, changes in operating conditions at the UE mayresult in a need to adjust wireless link parameters or antennaconfigurations to adapt to those changes. In some embodiments, changesin operating conditions at the UE may result in current wireless linksunderperforming or failing to meet current or recently updated UEconnectivity requirements at the UE. For example, the intelligentwireless carrier link management system or MANO in an embodiment maydetermine that an established wireless link optimized for highthroughput communication cannot meet the recently updated UEconnectivity requirements associated with a recently initiated softwareapplication requiring low latency communication. As another example, theintelligent wireless carrier link management system or MANO in anembodiment may determine that an established wireless link optimized forlow latency communication cannot meet the recently updated UEconnectivity requirements associated with a recently initiated softwareapplication requiring high throughput communication. In another example,the intelligent wireless carrier link management system or MANO in anembodiment may determine that an established wireless link transceivingnon-secure data communication cannot meet the recently updated UEconnectivity requirements associated with a recently initiated softwareapplication requiring transceiving of secure data.

In some embodiments, changes in operating conditions at the UE mayresult in current wireless links providing connectivity exceedingupdated UE connectivity requirements at the UE. For example, UE antennaconfigurations prioritizing high throughput may need to be adjusted inan embodiment in which the UE ceases executing software applicationsdriving the earlier need for high throughput. As another example, UEantenna configurations prioritizing low latency may need to be adjustedin an embodiment in which the UE ceases executing software applicationsdriving the earlier need for low latency. As yet another example, UEantenna configurations prioritizing security may need to be adjusted inan embodiment in which the UE ceases executing software applicationsdriving the earlier need for high security.

As described herein, these determinations whether the current UE antennaconfigurations meet connectivity requirements may be made at either theintelligent wireless carrier link management system at an individual UE,or may be made by the MANO of the enterprise mobile network, based onmetrics gathered from a pool of UEs, each executing an agent of theintelligent wireless carrier link management system. In someembodiments, determinations made at the intelligent wireless carrierlink management system as to whether the current UE antennaconfigurations meet connectivity requirements, and policy requirementsgathered or determined for the UE, may be made at each UE individuallyand communicated to the MANO of the enterprise mobile network. If thecurrent UE antenna configurations do not meet the connectivity, andenterprise profile requirements for the UE, this may indicate changes inUE antenna configuration or selection of RANs are required, and themethod may proceed to block 718 for optimal redistribution of wirelesslinks across a plurality of UEs by the MANO in order to meetconnectivity, and enterprise profile requirements for as many UEs in thepool as possible. If the current UE antenna configurations meet theconnectivity, and enterprise profile requirements gathered from all UEswithin the pool, this may indicate no need for changes in UE antennaconfiguration or RAN selections, and the method may proceed back toblock 710 to continue to gather updated connectivity metrics todetermine updated UE connectivity requirements, as well as updated UEpolicies and enterprise UE connectivity profiles. The UE may communicatethis status to the MANO. By repeating the loop between blocks 710 and716 in such a way, the MANO and intelligent wireless carrier linkmanagement system may routinely assess the wireless communication needsacross all UEs communicating via the enterprise mobile network andadaptively changing wireless link configurations in order to provide agreatest number of UEs within the pool access to wireless links capableof meeting their changing UE connectivity requirements. However, it isunderstood that the MANO may determine that this UE may need to haveadjustments made to reduce connectivity capacity to accommodate otherUEs in the pool of UEs if unused bandwidth or wireless link capacity isassigned to it but not needed in example embodiments.

The MANO in an embodiment may determine an optimal wireless linkdistribution across all UEs communicating via the enterprise mobilenetwork for meeting updated QoS requirements across the largest possiblenumber of UEs within the pool at block 718. Changes may be made for theUE executing the intelligent wireless link carrier management system asdetermined by the MANO and communicated to the UE. For example, in anembodiment described with reference to FIG. 2 , the ways in whichconnectivity metrics for wireless links 220 established between the UEpool 210 and the enterprise RAN and core infrastructure 230 impactsquality of communications between the pool 210 of UEs and the remotecloud network 250 or MEC metrics, as routed through various componentsof the enterprise RAN and core infrastructure 230 may vary over time asthe applications executed by these UEs changes, various UEs enter orleave the pool 210 of linked UEs, the capabilities of the UEs within thepool 210 changes (e.g., more 4G capable UEs 211 enter and more 5Gcapable UEs 212 exit), or the locations of various UEs within the pool210 changes. The MANO 236 in an embodiment addresses these issues byroutinely assessing the communication needs for the pool 210 of UEswirelessly linked to the enterprise RAN and core infrastructure 230operating a plurality of cellular and non-cellular RANs (e.g., 231 and232), APs (e.g., 233), and network cores (e.g., 234 and 235) andadjusting availability of resources at each of these RANs, APs, andcores to meet UE needs. This may be ongoing with all UEs in the pool 210of UEs, and may respond to each particular UE that determines a changein antenna configuration and utilization of RANs available as needed asin step 716.

For example, the MANO 236 in an embodiment may scale up computing orprocessing resources available at the 4G RAN 231, 5G RAN 232, 4G EPC234, or 5G core 235 experiencing congestion, high-latency, or lowthroughput. In such an embodiment, the MANO 236 may further work intandem with the intelligent wireless carrier link management system 214at one or more UEs in the pool 210 to take advantage of these scaled upcomputing or processing resources by transceiving at least a portion ofdata through the recently scaled up component of the enterprise RAN andcore infrastructure 230. As another example, the MANO 236 in anembodiment may increase the number of antennas transceiving data at the4G RAN 231, 5G RAN 232, or Wi-Fi AP 233 when one of these components ofthe enterprise RAN and core infrastructure 230 is experiencing hightraffic load. In such an embodiment, the MANO 236 may further work intandem with the intelligent wireless carrier link management system 214at one or more UEs in the pool 210 to take advantage of these newlyadded antennas by transceiving at least a portion of data through therecently activated antennas.

The MANO 236 in an embodiment may also operate to redistribute wirelesslinks between a plurality of UEs in the pool 210 and variousinfrastructure components (e.g., 4G RAN 231, 5G RAN 232, non-cellular AP233, 4G EPC 234, or 5G core 235) of the enterprise RAN and coreinfrastructure 230 to ensure UE connectivity requirements are met for asmany UEs in pool 210 as possible. In such an embodiment, the MANO 236may do so, for example, by assigning one or more wireless links capableof meeting a specific UE's connectivity requirements, as indicated byconnectivity metrics for those wireless links, to that specific UE. Morespecifically, the MANO 236 in such an example embodiment may assign awireless link with the 4G RAN 231, 5G RAN 232, or non-cellular AP 233having connectivity metrics indicating a high throughput to a UE withinpool 210 having a connectivity requirement for high throughput. Asanother example, the MANO 236 in such an example embodiment may assign awireless link with the 4G RAN 231, 5G RAN 232, or non-cellular AP 233having connectivity metrics indicating a low latency to a UE within pool210 having a connectivity requirement for low latency.

In some cases, UE connectivity requirements cannot be met for all UEs inthe pool 210. For example, the number of wireless links havingconnectivity metrics indicating high throughput may be less than thenumber of UEs in pool 210 that are requesting high throughput wirelesslinks. As another example, the number of wireless links havingconnectivity metrics indicating low latency may be less than the numberof UEs in pool 210 that are requesting low latency wireless links. Insuch scenarios, the MANO 236 may access enterprise UE connectivityprofiles from the subscription manager data preparation platform 237 todetermine which UEs in pool 210 should be given priority for wirelesslinks in high demand. Such enterprise UE connectivity profiles mayindicate a UE rank or priority status, as assigned to the UE by an ITprofessional of the enterprise. For example, a UE assigned to acorporate officer or key engineering or technical personnel of theenterprise may be given a higher UE rank or priority status incomparison to a UE assigned to a new employee or an employee whoseconnectivity requirements are lower or currently unused. As anotherexample, a UE designated for processing large volumes of data central tothe business operations of the enterprise may be given a highest UE rankor priority status. As yet another example, a UE located within acertain geographical area such as a secure portion of an enterprisecampus or a meeting room of an enterprise campus routinely used forsales or negotiations may be given a higher UE rank or priority status.By retrieving or accessing such enterprise UE connectivity profilesstored at the subscription manager data preparation platform 237 in anembodiment, the MANO 236 may assign wireless links in high demand to UEsin pool 210 indicating such a demand according to UE rank or prioritystatus. For example, the MANO 236 may assign high demand wireless linksto all UEs in pool 210 indicating such a demand in a highest UE rank orpriority status first, then in descending order of UE rank or prioritystatus until all high demand wireless links have been distributed.

At block 720, the MANO in an embodiment may determine a UE antennaconfiguration adjustment required to achieve the optimal wireless linkdistribution across all UEs. Antenna configuration adjustments at the UEmay include, for example, activation or deactivation of any availableantenna and any wireless protocol radio system at the UE. As describedherein, the MANO in an embodiment may increase or decrease capacity atone or more enterprise mobile network infrastructure components (e.g.,RANs, non-cellular APs, cores, or MECs), based on all of thisinformation gathered across all UEs communicating within the enterprisemobile network in order to optimize connectivity for all UEs. When theMANO adjusts capacity at one or more of such infrastructure componentsin such a way, the MANO may then redistribute wireless links across thepool of UEs communicating within the enterprise mobile network. In sucha way, the MANO may instruct the operation of the UEs, including the UEexecuting the method portions of FIG. 7 , in order to take advantage ofthis increased capacity at various infrastructure components or tocompensate for decreased capacity at various infrastructure components.The MANO may instruct the operation of the UEs in such embodiments bytransmitting an instruction to adjust UE antenna configuration directlyto a UE via OOB communications. The MANO may also adjust policies at oneor more cellular network cores in order to authorize those UEs to accesscommunications through those cellular network cores, as described ingreater detail below.

As an example of the MANO redistributing wireless links based onadjustments to capacity at various infrastructure components of theenterprise mobile network, in an embodiment described with reference toFIG. 3 , the MANO 320 may scale up computing or processing resourcesavailable at the 4G RAN 360 or 4G EPC 350 experiencing congestion,high-latency, or low throughput. In such an embodiment, the MANO 320 mayfurther work in tandem with the intelligent wireless carrier linkmanagement system at one or more UEs in the pool 340 to take advantageof these scaled up computing or processing resources by transceiving atleast a portion of data through the recently scaled up 4G RAN 360 or 4GEPC 350. For example, the MANO 320 may instruct one or more UEs in pool340, including the UE executing method portions of FIG. 7 , currentlytransceiving data via a wireless link between a first antenna at the UEand either the 5G RAN or non-cellular AP 330 to activate a secondantenna for transceiving of data via a wireless link to the 4G RAN 360.Similarly, the MANO 320 may instruct these one or more UEs in pool 340currently transceiving data via a wireless link between a first antennaat the UE and the 4G RAN 360 to deactivate this first antenna when theMANO 320 decreases computing or processing resources available at the 4GRAN 360.

As another example, the MANO 320 in an embodiment may increase thenumber of antennas (e.g., 362, 366, or 371) transceiving data at the 4GRAN 360 when the 4G RAN 360 is experiencing high traffic load. In suchan embodiment, the MANO 320 may further work in tandem with theintelligent wireless carrier link management system at one or more UEsin the pool 340 to take advantage of these newly added antennas bytransceiving at least a portion of data through the recently activatedantennas. For example, the MANO 320 may instruct one or more UEs in pool340, including the UE executing method portions of FIG. 7 , currentlytransceiving data via a wireless link between a first antenna at the UEand either the 5G RAN or non-cellular AP 330 to activate a secondantenna for transceiving of data via a wireless link to these newlyactivated antennas at the 4G RAN 360. Similarly, the MANO 320 mayinstruct one or more UEs in pool 340, including the UE executing methodportions of FIG. 7 , currently transceiving data via a wireless linkbetween a first antenna at the UE and the 4G RAN 360 to deactivate thisfirst antenna when the MANO 320 decreases the number of antennasavailable at the 4G RAN 360.

As another example of the MANO redistributing wireless links based onadjustments to capacity at various infrastructure components of theenterprise mobile network, in an embodiment described with reference toFIG. 4 , the MANO 474 may scale up computing or processing resourcesavailable at the 5G RAN 480 or 5G core 470 experiencing congestion,high-latency, or low throughput. In such an embodiment, the MANO 474 mayfurther work in tandem with the intelligent wireless carrier linkmanagement system at one or more UEs in the pool 490, including the UEexecuting method portions of FIG. 7 , to take advantage of these scaledup computing or processing resources by transceiving at least a portionof data through the recently scaled up 5G RAN 480 or 5G core 470. Forexample, the MANO 474 may instruct one or more UEs in pool 490,including the UE executing method portions of FIG. 7 , currentlytransceiving data via a wireless link between a first antenna at the UEand either the 4G RAN or non-cellular AP to activate a second antennafor transceiving of data via a wireless link to the 5G RAN 480.Similarly, the MANO 474 may instruct one or more UEs in pool 490currently transceiving data via a wireless link between a first antennaat the UE and the 5G RAN 480 to deactivate this first antenna when theMANO 474 decreases computing or processing resources available at the 5GRAN 480.

As another example, the MANO 474 in an embodiment may increase thenumber of antennas (e.g., 401, 402, or 450) transceiving data at the 5GRAN 480 when the 5G RAN 480 is experiencing high traffic load. In suchan embodiment, the MANO 474 may further work in tandem with theintelligent wireless carrier link management system at one or more UEsin the pool 490, including the UE executing method portions of FIG. 7 ,to take advantage of these newly added antennas by transceiving at leasta portion of data through the recently activated antennas. For example,the MANO 474 may instruct one or more UEs in pool 490 currentlytransceiving data via a wireless link between a first antenna at the UEand either the 4G RAN or non-cellular AP to activate a second antennafor transceiving of data via a wireless link to one of the newlyactivated antennas at the 5G RAN 480. Similarly, the MANO 474 mayinstruct one or more UEs in pool 490 currently transceiving data via awireless link between a first antenna at the UE and the 5G RAN 480 todeactivate this first antenna when the MANO 474 decreases the number ofantennas available at the 5G RAN 480.

The MANO in various embodiments may also distribute or reroute wirelesslinks across the pool of UEs to redirect traffic away from certaininfrastructure components of the enterprise mobile network experiencinghigh traffic or congestion. For example, in an embodiment described withrespect to FIG. 3 , the MANO 320 may redirect traffic moving through the4G RAN 360 to access the 4G EPC 350 via the non-cellular AP 330, ratherthan through the 4G RAN 360 when one or more of the BBUs (e.g., 365,369, or 370) are experiencing heavy traffic loads. In such anembodiment, the MANO 320 may further work in tandem with the intelligentwireless carrier link management system at one or more UEs in the pool340, including the UE executing method portions of FIG. 7 , to terminatewireless links established with the 4G RAN 360 and establish wirelesslinks to the 4G EPC 350 via the non-cellular AP 330. For example, theMANO 320 may instruct one or more UEs in pool 340 currently transceivingdata via a wireless link between a first antenna at the UE and the 4GRAN 360 to deactivate the first antenna and to activate a second antennafor transceiving of data via a wireless link to the non-cellular AP 330.

As another example, in an embodiment described with reference to FIG. 4, the MANO may redirect traffic moving through the 5G RAN 480 to accessthe 5G core 470 via a non-cellular AP, rather than through the 5G RAN480 when one or more of the DUs (e.g., 410 or 412) or CUs (e.g., 431, or433) are experiencing heavy traffic loads. In such an embodiment, theMANO 474 may further work in tandem with the intelligent wirelesscarrier link management system at one or more UEs in the pool 490,including the UE executing method portions of FIG. 7 , to terminatewireless links established with the 5G RAN 480 and establish wirelesslinks to the 5G core 470 via a non-cellular AP. For example, the MANO474 may instruct one or more UEs in pool 490 currently transceiving datavia a wireless link between a first antenna at the UE and the 5G RAN 480to deactivate the first antenna and to activate a second antenna fortransceiving of data via a wireless link to the non-cellular AP. In anembodiment described with reference to FIG. 5 , the MANO 520 mayinstruct one or more UEs in pool 590 currently transceiving data via awireless link between a first antenna at the UE and the 5G RAN 580 todeactivate the first antenna and to activate a second antenna fortransceiving of data via a wireless link to the non-cellular AP 501.

The MANO in various embodiments may also distribute or reroute wirelesslinks across the pool of UEs as the connectivity requirements for thoseUEs change over time (e.g., requirements for high throughput or lowlatency). Activation of an additional antenna in an embodiment may beappropriate, for example, when a single antenna fails to providewireless service or data bandwidth of updated or current connectivitymetrics gathered at blocks 710 and 712 for the currently transceivingwireless link established via a first antenna at block 708. For example,the first wireless link established at block 708 may have beenestablished for high-throughput communication. In such an embodiment,the updated or current connectivity metrics gathered at blocks 710 and712 may indicate recent initiation of a latency-sensitive softwareapplication at the UE. The MANO in such an embodiment may identify suchUEs as requiring both high throughput and low latency communications. Insome cases, both of these requirements may be met by a single wirelesslink, such as, for example, a wireless link with a closely located 5GRAN experiencing low traffic conditions. In other cases, the MANO maydetermine the best way to satisfy both the low latency and highthroughput requirements, while simultaneously ensuring other UEs receivewireless links meeting their own connectivity and policy requirementsinvolves establishing two separate wireless links—one for highthroughput communications, and one for low latency communications. Inorder to satisfy both the low-latency and the high-throughputrequirements, the MANO in such an embodiment may determine a UE antennaconfiguration adjustment that activates a second antenna forestablishment of low-latency wireless links is appropriate.

As another example, the first wireless link established at block 708 mayhave been established for low-latency communication. In such anembodiment, the updated or current connectivity requirements gathered atblocks 710 and 712 may indicate recent initiation of athroughput-sensitive software application at the UE. The MANO, incoordination with the intelligent wireless carrier link managementssystem at the UE, in such an embodiment may determine a UE antennaconfiguration adjustment that activates a second antenna forestablishment of high throughput wireless links is appropriate.

In another example, the first wireless link established at block 708 mayhave been established for secure communication. In such an embodiment,the updated or current connectivity metrics gathered at blocks 710 and712 may indicate recent initiation of software application at the UEthat are not transceiving secure or sensitive information. The MANO, incoordination with the intelligent wireless carrier link managementssystem at the UE, in such an embodiment may identify such UEs asrequiring both secure and non-secure communications. In some cases, bothof these requirements may be met by a single wireless link, such as, forexample, a single wireless link transceiving all data securely,regardless of security requirement. In other cases, the MANO maydetermine the best way to satisfy both security requirements (e.g.,secure and non-secure), while simultaneously ensuring other UEs receivewireless links meeting their own connectivity and policy requirementsinvolves establishing two separate wireless links—one for securecommunications (e.g., via a cellular RAN and core), and one fornon-secure communications (e.g., via a non-cellular AP). In order tosatisfy both these security requirements, the MANO in such an embodimentmay determine a UE antenna configuration adjustment that activates asecond antenna for transceiving of non-secure information isappropriate.

In still another example, the first wireless link established at block708 may have been established for non-secure communication. In such anembodiment, the updated or current connectivity metrics gathered atblocks 710 and 712 may indicate recent initiation of softwareapplication at the UE that are transceiving secure or sensitiveinformation. The MANO, in coordination with the intelligent wirelesscarrier link managements system at the UE, in such an embodiment maydetermine a UE antenna configuration adjustment that activates a secondantenna for transceiving of secure information is appropriate.

In yet another example, the first wireless link established at block 708may have been established with a 5G RAN/core. In such an embodiment, theupdated or current UE connectivity metrics gathered at blocks 710 and712 may indicate this wireless link fails to meet all of the UEconnectivity requirements at the UE. The MANO, in coordination with theintelligent wireless carrier link managements system at the UE, in suchan embodiment may determine a UE antenna configuration adjustment thatactivates a second antenna for establishment of a second wireless linkwith another RAN (e.g., 4G RAN, non-cellular AP, or 5G RAN) may beappropriate in order to increase overall performance of the connectivitymetrics at the UE.

As another example, the first wireless link established at block 708 mayhave been established with a 4G RAN/EPC. In such an embodiment, theupdated or current UE connectivity metrics gathered at blocks 710 and712 may indicate this wireless link fails to meet all the UEconnectivity requirements at the UE. The MANO, in coordination with theintelligent wireless carrier link managements system at the UE, in suchan embodiment may determine a UE antenna configuration adjustment thatactivates a second antenna for establishment of a second wireless linkwith another RAN (e.g., 4G RAN, non-cellular AP, or 5G RAN) may beappropriate in order to increase overall performance of the connectivitymetrics at the UE.

In still another example, the first wireless link established at block708 may have been established with a non-cellular AP. In such anembodiment, the updated or current connectivity metrics gathered atblocks 710 and 712 may indicate this wireless link fails to meet the UEconnectivity requirements at the UE. The MANO, in coordination with theintelligent wireless carrier link managements system at the UE, in suchan embodiment may determine a UE antenna configuration adjustment thatactivates a second antenna for establishment of a second wireless linkwith another RAN (e.g., 4G RAN, non-cellular AP, or 5G RAN) may beappropriate in order to increase overall performance to meet UEconnectivity metrics at the UE.

Deactivation of an antenna in an embodiment may be appropriate, forexample, when changes in operating conditions at the UE result incurrent wireless links (e.g., as established at block 708) providingconnectivity exceeding updated connectivity metrics at the UE gatheredat blocks 710 and 712. For example, the MANO, in coordination with theintelligent wireless carrier link managements system at the UE, in anembodiment in which a current UE antenna configuration prioritizes highthroughput, but the UE recently ceased executing software applicationsdriving the earlier need for high throughput may determine a UE antennaconfiguration adjustment that deactivates the antenna transceiving on ahigh throughput wireless link due to the adjustment down of the capacityrequirement of the UE connectivity requirement based on the gatheredconnectivity metrics. As another example, the MANO, in coordination withthe intelligent wireless carrier link managements system at the UE, inan embodiment in which a current UE antenna configuration prioritizeslow latency, but the UE recently ceased executing software applicationsdriving the earlier need for low latency may determine a UE antennaconfiguration adjustment that deactivates the antenna transceiving on alow latency wireless link. As yet another example, the MANO, incoordination with the intelligent wireless carrier link managementssystem at the UE, in an embodiment in which a current UE antennaconfiguration prioritizes secure transmission, but the UE recentlyceased executing software applications driving the earlier need for highsecurity may determine a UE antenna configuration adjustment thatdeactivates the antenna transceiving on a secure wireless link. Theseare only a few examples of situations in which the MANO, in coordinationwith the intelligent wireless carrier link managements system at the UE,in an embodiment may determine a UE antenna configuration adjustment isappropriate. The method for determining a UE antenna configurationadjustment may then end.

FIG. 8 is a flow diagram illustrating a method of adjusting a UE antennaconfiguration, based on adjustments determined at the UE or by a MANO ofthe enterprise mobile network according to an embodiment of the presentdisclosure. As described herein, UE antenna configuration adjustments inan embodiment may also be determined by a Management and OrchestrationModule (MANO) operating remotely from each of the UEs within theenterprise mobile network. Such determinations may be made, in variousembodiments described herein, in order to leverage changes in capacityat various infrastructure components of the RANs, non-cellular APs, andcores comprising the enterprise mobile network, as made by the MANO, tooptimize performance across each of these infrastructure components andthe pool of UEs communicating within the network.

At block 802, the MANO in an embodiment may determine a UE antennaconfiguration adjustment. The MANO in various embodiments describedherein may determine an optimal distribution of wireless links havingvarying connectivity metrics across a pool or UEs in communication viathe enterprise mobile network in order to meet connectivity requirementsdetermined based on gathered connectivity metrics and UE enterpriseprofile requirements at a largest number of those UEs to optimizeconnectivity among the linked or managed UEs, as described withreference to FIG. 7 at block 718. For example, the MANO in an embodimentmay distribute or reroute wireless links across the pool of UEs in orderto take advantage of recent scaling of processing resources at variousinfrastructure components (e.g., RANs, non-cellular APs, MEC, orcellular network cores) within the enterprise mobile network. As anotherexample, the MANO may distribute or reroute wireless links across thepool of UEs to redirect traffic away from certain infrastructurecomponents of the enterprise mobile network experiencing high traffic orcongestion. As yet another example, the MANO may distribute or reroutewireless links across the pool of UEs as the connectivity requirementsfor those UEs change over time (e.g., requirements for high throughputor low latency).

As described with reference to block 720 of FIG. 7 , the MANO mayfurther determine one or more antenna configuration adjustments atvarious UEs that are required in order to achieve the optimal wirelesslink distribution across all UEs communicating within the enterprisemobile network. For example, the MANO may instruct activation ordeactivation of an antenna at a UE in response to an increase ordecrease capacity at one or more enterprise mobile networkinfrastructure components (e.g., RANs, non-cellular APs, cores, orMECs). As another example, the MANO may activate or deactivate antennasin order to redirect traffic away from certain infrastructure componentsof the enterprise mobile network experiencing high traffic orcongestion. As yet another example, the MANO in an embodiment mayactivate or deactivate UE antennas as the connectivity requirements forUEs change over time (e.g., requirements for high throughput or lowlatency).

At block 804, the MANO in an embodiment may adjust UE policies atnetwork cores to accommodate UE antenna configuration adjustments. Forexample, in an embodiment described with reference to FIG. 2 , the MANO237 may increase capacity at the 4G RAN 231 and determine one or more ofthe WiFi UEs 213 not currently authorized for communication via the 4Gsystem should perform a UE antenna configuration adjustment to add asecond antenna for transceiving data with the 4G system. In order tofacilitate execution of such a UE antenna configuration adjustment, theMANO 236 may adjust policies stored at the 4G EPC 234 to authorize thoseWi-Fi UEs 213 to communicate via the 4G network.

For example, in an embodiment described with reference to FIG. 3 , theHome Subscriber Server (HSS) 312 may store policy information for theplurality of UEs in pool 340. These policies may inform or dictate thetypes of wireless communication networks with which each UE in pool 340associated with a given policy may establish wireless connections, basedon detected network RAN and core network conditions including linkperformance requirements, security requirements, types of networkssupported by a given UE, or other factors in various embodiments. Forexample, the HSS 312 may store a separate policy for each of the UEs inthe pool 340 that identifies one or more subscriptions with which agiven UE may be associated, defining which RANs (e.g., 4G RAN 360),non-cellular APs (e.g., AP 330), or cellular network cores (e.g., 4G EPC350) that UE may access, and the priority for accessing them. Forexample, a subscription may grant 4G compatible UEs in pool 340 accessto the non-cellular AP 330, 4G RAN 360 or the 4G EPC 350.

As another example, the MANO 237 may increase capacity at, or shiftcapacity to, the 5G RAN 232, and determine one or more of the 4G UEs211, or WiFi UEs 213 not currently authorized for communication via the5G system should perform a UE antenna configuration adjustment to add asecond antenna for transceiving data with the 5G system. In order tofacilitate execution of such a UE antenna configuration adjustment, theMANO 236 may adjust policies stored at the 5G core 235 to authorizethose 4G UEs 211 or Wi-Fi UEs 213 to communicate via the 5G network.

In an embodiment described with reference to FIG. 5 , the Unified DataRepository (UDR) 506 may store policy information for the plurality ofUEs in pool 490. These policies may inform or dictate the types ofwireless communication networks with which each UE in pool 490associated with a given policy may establish wireless connections, basedon RAN and associated core network conditions link performancerequirements, security requirements, types of networks supported by agiven UE, or other factors in various embodiments. This assessment ofRAN and core operating conditions may further determination the UEantenna configuration adjustments for UEs along with the UE connectivityrequirements across each of the plural UEs as well as enterprise profilerequirements for UEs on an enterprise-provided mobile network withplural RANs. For example, a subscription given in such a policy maygrant 5G compatible UEs in pool 490 access to the non-cellular AP 501,5G RAN 550 or the 5G core 570. These policies may further prioritizevarious QoS requirements for each UE. For example, each UE may beassociated with a minimum QoS requirement such as a minimum RSSImagnitude of 80 (e.g., higher than −80 dBm). As another example, thesepolicies may designate a highest priority requirement, such asthroughput, latency, or security.

The MANO may instruct the intelligent wireless carrier link managementsystem at a UE to execute an adjustment to the UE wireless antennaconfiguration at block 806. The MANO may transmit an instruction to theintelligent wireless carrier link managements system at the UE toperform the antenna configuration adjustment determined at block 720 ofFIG. 7 , in an embodiment. For example, in an embodiment described withreference to FIG. 2 , the MANO 236 may increase capacity at the 4G RAN231 in order to optimize performance of wireless links across the pool210 of UEs. In such an embodiment, the MANO 235 may then transmit aninstruction to one or more of the 4G UEs 211 or the 5G UEs 212 toactivate a second antenna at that UE for transceiving data specificallywith the 4G RAN 231 that has recently increased capacity. For example,in an embodiment described with reference to FIG. 6 , a UE informationhandling system 600 may have an established wireless link with a 5G RAN(e.g., 620) via a first antenna within WWAN antenna systems 653. TheMANO in an embodiment may transmit an instruction to the UE 600 toactive a second antenna within WWAN antenna systems 653, and toestablish a second wireless link via this second antenna to a 4G RAN.The MANO in such an embodiment may transmit this instruction via theexisting wireless link between the WWAN interface device 650 and the 5GRAN 620, or via 00B communications with the embedded controller 636.

As another example, in an embodiment described with reference to FIG. 2, the MANO 236 may increase capacity at the 5G RAN 232 in order tooptimize performance of wireless links across the pool 210 of UEs. Insuch an embodiment, the MANO 235 may then transmit an instruction to oneor more of the 5G UEs 212 to activate a second antenna at that UE fortransceiving data specifically with the 5G RAN 231 that has recentlyincreased capacity. For example, in an embodiment described withreference to FIG. 6 , a UE information handling system 600 may have anestablished wireless link with a 4G RAN (e.g., 620) via a first antennawithin WWAN antenna systems 653. The MANO in an embodiment may transmitan instruction to the UE 600 to active a second antenna within WWANantenna systems 653, and to establish a second wireless link via thissecond antenna to a 5G RAN. The MANO in such an embodiment may transmitthis instruction via the existing wireless link between the WWANinterface device 650 and the 4G RAN 620, or via OOB communications withthe embedded controller 636.

In still another example, in an embodiment described with reference toFIG. 2 , the MANO 236 may increase capacity at the non-cellular AP 233in order to optimize performance of wireless links across the pool 210of UEs. In such an embodiment, the MANO 235 may then transmit aninstruction to one or more of the Wi-Fi UEs 213 to activate a secondantenna at that UE for transceiving data specifically with thenon-cellular AP 233 that has recently increased capacity. For example,in an embodiment described with reference to FIG. 6 , a UE informationhandling system 600 may have an established wireless link with acellular RAN (e.g., 620) via a first antenna within WWAN antenna systems653. The MANO in an embodiment may transmit an instruction to the UE 600to active a second antenna within WLAN antenna systems 663, and toestablish a second wireless link via this second antenna to the WLAN AP621. The MANO in such an embodiment may transmit this instruction viathe existing wireless link between the WWAN interface device 650 and theRAN 620, or via OOB communications with the embedded controller 636.

At block 808, the intelligent wireless carrier link management system inan embodiment may determine whether the received antenna configurationadjustment includes addition or subtraction of a UE antenna. Asdescribed herein, UE antenna configuration adjustments in an embodimentmay be determined by the MANO, as described in FIG. 7 at block 720. Uponsuch receipt of instruction indication such a determination made by theMANO, the intelligent wireless carrier link management system mayexecute the determined UE antenna configuration adjustment.

This adjustment may prompt addition or activation of a second antenna ata UE in an embodiment. For example, the MANO in an embodiment maydetermine a second antenna should be activated in order to transceivedata with a RAN or non-cellular AP whose capacity has recently beenincreased by the MANO (e.g., as described with respect to block 720 inFIG. 7 ). As another example, the MANO in an embodiment may determine anantenna transceiving data with a RAN or non-cellular AP that the MANOhas recently scaled down should be deactivated. In yet another example,the MANO in an embodiment may instruct activation of a second antennafor transceiving data via a wireless link with non-congested RAN ornon-cellular AP, or deactivation of a first antenna currentlytransceiving data via a wireless link with a congested RAN ornon-cellular AP in order to reroute traffic to avoid the congested RANor non-cellular AP. In still another embodiment, the MANO may determinethat a UE currently transceiving data on a wireless link optimized for afirst connectivity requirement should activate a second antennaconfigured to optimize communications for a second connectivityrequirement, as described above with respect to FIG. 7 at block 720. Ifthe UE antenna configuration adjustment received from the MANO involvessubtraction or deactivation of an antenna, the method may proceed toblock 810 for such deactivation. If the UE antenna configurationadjustment received from the MANO involves addition or activation of asecond antenna, the method may proceed to block 812 for such activation.

In an embodiment in which the UE antenna configuration adjustmentreceived from the MANO involves deactivation of an antenna, theintelligent wireless carrier link management system may terminate thewireless link transceiving via the antenna identified for deactivationwithin the UE antenna configuration adjustment and deactivate thatantenna at block 810. For example, in an embodiment in which the UEantenna configuration adjustment indicates that the UE should deactivatean antenna due to decreased need to communicate data via a low-latencywireless link, the UE may deactivate the antenna transceiving data via alow-latency wireless link. As another example, in an embodiment in whichthe UE antenna configuration adjustment indicates that the UE shoulddeactivate an antenna due to decreased need to communicate data via ahigh throughput wireless link, the UE may deactivate the antennatransceiving data via a high throughput wireless link. In still anotherexample, in an embodiment in which the UE antenna configurationadjustment indicates that the UE should deactivate an antenna due todecreased need to communicate secure data, the UE may deactivate theantenna transceiving secure data. In yet another example, in anembodiment in which the UE antenna configuration adjustment indicatesthat the UE should deactivate an antenna due to decreased need tocommunicate non-secure data, the UE may deactivate the antennatransceiving non-secure data.

The intelligent wireless carrier link management system in an embodimentmay deactivate an antenna by decreasing or ceasing power delivery to theantenna, or by placing the antenna in an idle or low-power mode. Forexample, in an embodiment described with respect to FIG. 6 , theintelligent wireless carrier link management system 612 may instruct thePMU 632 to cease or decrease power delivery to an antenna within theWWAN antenna systems 653, or an antenna within the WLAN antenna system663. In another example, the intelligent wireless carrier linkmanagement system 612 may instruct the WWAN network interface device 650or the WLAN network interface device 660 to enter an idle or low-powermode.

At block 812, in an embodiment in which the UE antenna configurationadjustment received from the MANO involves activation of a secondantenna, the intelligent wireless carrier link management system mayactivate an antenna capable of establishing a wireless link withproperties identified within the UE antenna configuration adjustment.For example, in an embodiment described with reference to FIG. 6 inwhich the UE antenna configuration adjustment instructs activation of anantenna for establishment of a high throughput wireless link, theintelligent wireless carrier link management system 612 may identify aRAN 620 or a non-cellular AP 621 generating beacon data indicating ahighest available throughput measurement. The intelligent wirelesscarrier link management system 612 may then activate an antenna withinthe WWAN antenna systems 653 for high throughput communication with theRAN 620 or activate an antenna within the WLAN antenna systems 663 forhigh throughput communication with the non-cellular AP 621, dependingupon which of the two (e.g., RAN 620 or AP 621) generate beacon dataindicating the highest available throughput.

As another example, in an embodiment in which the UE antennaconfiguration adjustment instructs activation of an antenna forestablishment of a low latency wireless link, the intelligent wirelesscarrier link management system 612 may identify a RAN 620 or anon-cellular AP 621 generating beacon data indicating a lowest availablelatency measurement. The intelligent wireless carrier link managementsystem 612 may then activate an antenna within the WWAN antenna systems653 for low latency communication with the RAN 620 or activate anantenna within the WLAN antenna systems 663 for low latencycommunication with the non-cellular AP 621, depending upon which of thetwo (e.g., RAN 620 or AP 621) generate beacon data indicating the lowestavailable latency.

In yet another example, in an embodiment in which the UE antennaconfiguration adjustment instructs activation of an antenna forestablishment of a secure wireless link, the intelligent wirelesscarrier link management system 612 may identify a RAN 620 or anon-cellular AP 621 generating highest QoS measurements. The intelligentwireless carrier link management system 612 may then activate an antennawithin the WWAN antenna systems 653 for secure communication with theRAN 620 or activate an antenna within the WLAN antenna systems 663 forcommunication vi aa VPN tunnel with the non-cellular AP 621, dependingupon which of the two (e.g., RAN 620 or AP 621) generate beacon dataindicating highest QoS measurements.

In another example, in which the MANO determines the UE antennaconfiguration adjustment based on changes in capacity at variousenterprise mobile network infrastructure components, the UE antennaconfiguration adjustment may specifically identify the RAN or AP towhich the newly activated antenna should connect. For example, in anembodiment described with reference to FIG. 2 , the intelligent wirelesscarrier link management system 214 may receive a UE antennaconfiguration adjustment from the MANO 236 to establish a wireless linkwith the 4G RAN 231 via the newly activated antenna in order to takeadvantage of recently increased capacity at the 4G RAN 231. As anotherexample, the intelligent wireless carrier link management system 214 mayreceive a UE antenna configuration adjustment from the MANO 236 toestablish a wireless link with the 5G RAN 232 via the newly activatedantenna in order to take advantage of recently increased capacity at the5G RAN 232. As yet another example, the intelligent wireless carrierlink management system 214 may receive a UE antenna configurationadjustment from the MANO 236 to establish a wireless link with thenon-cellular AP 233 via the newly activated antenna in order to takeadvantage of recently increased capacity at the non-cellular AP 233.

Upon receipt of such a UE antenna configuration adjustment specificallyidentifying a RAN or non-cellular AP, the intelligent wireless carrierlink management system may activate an antenna within a networkinterface device capable of establishing wireless links with thespecifically identified RAN or non-cellular AP. For example, in anembodiment described with respect to FIG. 6 in which the UE antennaconfiguration adjustment specifically identifies a 4G RAN, theintelligent wireless carrier link management system 612 may activate anantenna within WWAN antenna systems 653 for establishment of a wirelesslink to a 4G RAN (e.g., 620). As another example, in an embodiment inwhich the UE antenna configuration adjustment specifically identifies a5G RAN, the intelligent wireless carrier link management system 612 mayactivate an antenna within WWAN antenna systems 653 for establishment ofa wireless link to a 5G RAN (e.g., 620). As yet another example, in anembodiment in which the UE antenna configuration adjustment specificallyidentifies a non-cellular AP, the intelligent wireless carrier linkmanagement system 612 may activate an antenna within WLAN antennasystems 663 for establishment of a wireless link to a non-cellular AP(e.g., 621).

The UE may establish a wireless link via the newly activated antennapursuant to the UE antenna configuration adjustment at block 814. Forexample, in an embodiment described with reference to FIG. 6 in whichthe UE antenna configuration adjustment instructs activation of anantenna for establishment of a high throughput wireless link, theintelligent wireless carrier link management system 612 may direct theWWAN network interface device 650 to establish a wireless link with aRAN 620 or direct the WLAN network interface device 660 to establish awireless link with a non-cellular AP 621 (whichever of the RAN 620 or AP621 generates beacon data indicating a highest available throughputmeasurement) via the newly activated WWAN or WLAN antenna. As anotherexample, the intelligent wireless carrier link management system 612 maydirect the WWAN network interface device 650 to establish a wirelesslink with a RAN 620 or direct the WLAN network interface device 660 toestablish a wireless link with a non-cellular AP 621 (whichever of theRAN 620 or AP 621 generates beacon data indicating a lowest availablelatency measurement) via the newly activated WWAN or WLAN antenna. Asyet another example, the intelligent wireless carrier link managementsystem 612 may direct the WWAN network interface device 650 to establisha wireless link with a RAN 620 or direct the WLAN network interfacedevice 660 to establish a wireless link and VPN tunnel with anon-cellular AP 621 (whichever of the RAN 620 or AP 621 generates beacondata indicating a highest QoS measurement) via the newly activated WWANor WLAN antenna.

In another example, in an embodiment in which the UE antennaconfiguration adjustment specifically identifies a 4G RAN, theintelligent wireless carrier link management system 612 may direct theWWAN network interface device 650 to establish a wireless link to a 4GRAN (e.g., 620), via the newly activated antenna within the WWAN antennasystem 653. As another example, in an embodiment in which the UE antennaconfiguration adjustment specifically identifies a 5G RAN, theintelligent wireless carrier link management system 612 may direct theWWAN network interface device 650 to establish a wireless link to a 5GRAN (e.g., 620), via the newly activated antenna within the WWAN antennasystem 653. In yet another example, in which the UE antennaconfiguration adjustment specifically identifies a non-cellular AP, theintelligent wireless carrier link management system 612 may direct theWLAN network interface device 660 to establish a wireless link to anon-cellular AP (e.g., 621), via the newly activated antenna within theWLAN antenna system 663. The method for executing a UE antennaconfiguration adjustment may then end.

The blocks of the flow diagrams of FIGS. 7 through 8 or steps andaspects of the operation of the embodiments herein and discussed aboveneed not be performed in any given or specified order. It iscontemplated that additional blocks, steps, or functions may be added,some blocks, steps or functions may not be performed, blocks, steps, orfunctions may occur contemporaneously, and blocks, steps or functionsfrom one flow diagram may be performed within another flow diagram.

Information handling systems, modules, resources, or programs that arein communication with one another need not be in continuouscommunication with each other, unless expressly specified otherwise. Inaddition, information handling systems, modules, resources, or programsthat are in communication with one another can communicate directly orindirectly through one or more intermediaries.

Although only a few exemplary embodiments have been described in detailherein, those skilled in the art will readily appreciate that manymodifications are possible in the exemplary embodiments withoutmaterially departing from the novel teachings and advantages of theembodiments of the present disclosure. Accordingly, all suchmodifications are intended to be included within the scope of theembodiments of the present disclosure as defined in the followingclaims. In the claims, means-plus-function clauses are intended to coverthe structures described herein as performing the recited function andnot only structural equivalents, but also equivalent structures.

The above-disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover any andall such modifications, enhancements, and other embodiments that fallwithin the scope of the present invention. Thus, to the maximum extentallowed by law, the scope of the present invention is to be determinedby the broadest permissible interpretation of the following claims andtheir equivalents, and shall not be restricted or limited by theforegoing detailed description.

What is claimed is:
 1. An information handling system of a managementand orchestration module (MANO) comprising: a processor executing codeinstructions configured to: determine user equipment device (UE)connectivity requirements from UE connectivity metrics received from afirst UE via an out of band communication to the MANO, for a pluralityof UEs, including the first UE, managed by the MANO; determineenterprise profile requirements for the plurality of UEs including thefirst UE and detected network conditions of a plurality of wirelessprotocol radio access networks (RANs) and associated cores of anenterprise-provided mobile network; generate an optimal wireless linkdistribution across the plurality of UEs based on the UE connectivityrequirements, enterprise profile requirements of the plurality of UEs,and detected network conditions of the RANs and associated cores of theenterprise-provided mobile network; and determine an initial antennaconfiguration adjustment for the first UE instructing selection of afirst wireless link via a first antenna, selected to meet the UEconnectivity requirement relative to wireless links assigned to theplurality of UEs according to the optimal wireless link distribution;and a network interface device to transmit the initial antennaconfiguration adjustment to the first UE.
 2. The information handlingsystem of claim 1, wherein the initial antenna configuration adjustmentinvolves deactivation of a second antenna and establishment of the firstwireless link via the first antenna and a first wireless protocol radioto meet the UE connectivity requirement received from the first UE andto meet the optimal wireless link distribution of the plurality of UEson the enterprise-provided mobile network.
 3. The information handlingsystem of claim 1, wherein the enterprise profile requirements of theplurality of UEs includes enterprise determined rankings of theplurality of UEs based on minimum capacity requirements, quality ofservice requirements, or security requirements associated with each ofthe plurality of UEs and its associate user.
 4. The information handlingsystem of claim 1, wherein the UE connectivity requirement received fromthe first UE is a high-throughput requirement for the first wirelesslink.
 5. The information handling system of claim 1, wherein the UEconnectivity requirement received from the first UE is a low latencyrequirement for the first wireless link.
 6. The information handlingsystem of claim 1, wherein the UE connectivity requirement received fromthe first UE is a security requirement for the first wireless link. 7.The information handling system of claim 1, wherein the UE connectivityrequirement is defined in a user-selected enterprise UE connectivityprofile retrieved from a subscription manager data preparation platformof the enterprise mobile network.
 8. The information handling system ofclaim 1, wherein the initial antenna configuration adjustment involves aselection of one or more antennas and associated wireless protocolradios to increase or decrease wireless link capacity to meet the UEconnectivity requirement for the first UE as well the correspondingoptimal wireless link distribution of the plurality of UEs on theenterprise-provided mobile network.
 9. The information handling systemof claim 1 further comprising: the processor executing code instructionsof the MANO to: determine the UE connectivity requirement for which thefirst wireless link is optimized no longer applies to the first UE;determining an updated antenna configuration adjustment involvingadjustment to the wireless link capacity provided to the first UE fromthe initial antenna configuration adjustment; and the network interfacedevice transmitting the updated UE antenna configuration adjustment tothe first UE to meet an updated UE connectivity requirement and acorresponding updated optimal wireless link distribution of theplurality of UEs on the enterprise-provided mobile network.
 10. A methodof adjusting an antenna configuration at a first User Equipment device(UE) to optimize wireless links across a plurality of UEs operating onan enterprise-provided mobile network, comprising: transmitting an outof band communication, via a network interface device, UE connectivityrequirements for the first UE based on UE connectivity metricsindicating executing software applications on the first UE and qualityof service levels of available wireless links to a management andorchestration module (MANO) for an enterprise; receiving, via thenetwork interface device, of an antenna configuration adjustment for thefirst UE describing an adjustment to a current antenna configuration;instructing, according to the received antenna configuration adjustmentfor the first UE, establishment of a first wireless link via a firstantenna of the first UE required to meet a wireless link configurationassigned to the first UE according to an optimal wireless linkdistribution determined for the plurality of UEs communicating anenterprise mobile network by the MANO; and activating a first antennaand first wireless protocol radio to establish the first wireless linkwith a first radio access network (RAN) of the enterprise-providedmobile network in accordance with the antenna configuration adjustment,wherein the optimal wireless link distribution is to maximize aproportion of the plurality of UEs operating on the enterprise-providedmobile network that can establish wireless links capable of meeting UEconnectivity requirements associated with each of the plurality of UEs,enterprise profile requirements of the plurality of UEs, and detectednetwork conditions of the RANs and associated cores of theenterprise-provided mobile network.
 11. The method of claim 10, whereinthe UE connectivity requirement for which the first wireless link isoptimized is a high-throughput requirement.
 12. The method of claim 10,wherein the UE connectivity requirement for which the first wirelesslink is optimized is a low latency requirement.
 13. The method of claim10, wherein the UE connectivity requirement for which the first wirelesslink is optimized is a security requirement.
 14. The method of claim 10,wherein the antenna configuration adjustment involves a selection of oneor more antennas and associated wireless protocol radios to increase ordecrease wireless link capacity to meet the UE connectivity requirementfor the first UE as well the corresponding optimal wireless linkdistribution of the plurality of UEs on the enterprise-provided mobilenetwork.
 15. The method of claim 10, wherein the received antennaconfiguration adjustment further includes an assessment by the MANO ofenterprise profile requirements determining ranking of the first UErelative to the plurality of UEs on the enterprise-provided mobilenetwork based on capacity or quality of service minimums established forthe plurality of UEs.
 16. An information handling system of a userequipment device (UE) comprising: a processor executing codeinstructions of an intelligent wireless carrier link management systemto gather connectivity metrics of the UE indicating executing softwareapplications on the UE and quality of service levels of availablewireless links to the UE; a first network interface device to receive aUE antenna configuration adjustment from an enterprise mobile networkManagement and Orchestration Module (MANO) involving activation of anantenna and establishment of a first wireless link to a specificallyidentified Radio Access Network (RAN) or specifically identifiednon-cellular Access Point (AP) within the enterprise mobile network,where the UE antenna configuration adjustment is based on UEconnectivity requirements determined from the gathered UE connectivitymetrics, enterprise profile requirements indicating ranking of the UEamong a plurality of UEs on an enterprise-provided mobile network, anddetected network conditions of the RANs and associated cores of theenterprise-provided mobile network; the intelligent wireless carrierlink management system configured to identify an antenna capable ofcommunication with the specifically identified RAN or specificallyidentified non-cellular AP and establish the first wireless link,pursuant to the UE antenna configuration adjustment; and a radiooperating under the specifically identified RAN or specificallyidentified non-cellular AP to transceive data, via the first wirelesslink, with the specifically identified RAN or specifically identifiednon-cellular AP within the enterprise-provided mobile network havingwireless link capacity recently shifted to the UE by the MANO to meet anoptimal wireless link distribution among the plurality of UEs on theenterprise-provided mobile network.
 17. The information handling systemof claim 15, wherein the intelligent wireless carrier link managementsystem is configured to receive the UE antenna configuration adjustmentfrom the MANO via out-of-band (OOB) communications.
 18. The informationhandling system of claim 15, wherein the intelligent wireless carrierlink management system is configured to transmit the gatheredconnectivity metrics of the UE indicating executing softwareapplications on the UE and quality of service levels of availablewireless links to the UE to the MANO via out-of-band (OOB)communications to determine the UE connectivity requirements.
 19. Theinformation handling system of claim 15, wherein the intelligentwireless carrier link management system is configured to determine theUE connectivity requirements of the UE from the gathered UE connectivitymetrics of the UE indicating executing software applications on the UEand quality of service levels of available wireless links to the UE andto transmit the UE connectivity requirements to the MANO.
 20. Theinformation handling system of claim 15, wherein the antennaconfiguration adjustment involves a selection of one or more antennasand associated wireless protocol radios to increase or decrease wirelesslink capacity to meet the UE connectivity requirement for the UE as wellas a corresponding optimal wireless link distribution of the pluralityof UEs on the enterprise-provided mobile network.